Skip to main content
GullySystem
Professional services

Interview Scheduling for Recruitment agencies

Arrange interview rounds around candidate and panel availability.

Applicant Tracking

Does this function belong in your operation?

Use when interviews involve several participants or rounds.

An application is ready for interview.

Interview rounds are lined up between the candidate, the hiring manager and the client’s panel, with calendar slots held. Feedback from each round is chased and recorded. Rescheduled calls keep their history.

Bring the records the workflow depends on.

  • Candidate contacts
  • Panel availability
  • Round requirements

Outputs to check

  • Confirmed interview schedule
  • Reschedule and attendance history
  • Round completion record

Follow the interview scheduling workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Define the round

    Record required interviewers, format and expected duration.

  2. 2. Find availability

    Check candidate and panel schedules without double-booking.

  3. 3. Confirm the slot

    Retain time zone, location and joining instructions.

  4. 4. Manage changes

    Record cancellations or rescheduling and track communication status.

  5. 5. Record attendance

    Pass the completed-round reference to candidate tracking and feedback collection.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

HR executive

Fixes the slot, sends the invitation and prints tomorrow’s list for the front desk.

Panel member

Sees their own interviews for the week and opens the CV before the candidate sits down.

Front desk

Knows who is expected, marks them arrived, and tells HR when somebody has been waiting half an hour.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Panel cancellation

Find an alternative slot and record who was informed.

Candidate no-show

Keep the outcome distinct from rejection and route the next decision to recruitment.

Time-zone mismatch

Confirm the displayed time and zone before issuing revised joining instructions.

Can this work independently?

Scheduling needs candidate, vacancy and panel details. It can use locally maintained calendars; external calendar synchronisation and message delivery require supported connections. Candidate-stage updates and panel scoring are separate records linked by the interview reference.

Systems and records it connects with

  • Candidate tracking: Application identifiers, recruitment stages and hiring outcomes.
  • Collaboration management: Panel assignments, feedback and recorded hiring decisions.
  • External calendar: Supported interview availability and event updates, subject to account access.
  • WhatsApp: Permitted message content and channel delivery responses.

Configure, test and introduce the workflow.

  • You tell us how selection runs, from screening to final talk. You get a written outline of the rounds and fields. Keep it plain.
  • Panel members share their calendars. You see how free time appears on the scheduling screen. Invitation and reminder wording is agreed with you. A test message reaches your own phones.
  • A real hiring round is scheduled on the trial. You mark the rough edges, and they are corrected. Small flaws appear. The recruiter team is trained on rescheduling and recording outcomes. Old sheets are retired.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Interviewers are not double-booked.
  • Changed slots appear consistently.
  • Completed rounds retain outcomes.
Recruitment agencies

How the business operates.

The fee is earned on joining day. It is kept only if the candidate is still at the desk when the replacement window closes. Most agencies watch the first half of that closely and the second half not at all.

Mandate and job description register

Hold each client requirement with its fee terms, replacement clause, number of positions and the recruiter it belongs to, so nobody works a mandate that closed last week.

Candidate pipeline

Move candidates through sourced, screened, submitted, interviewed, offered and joined, with a duplicate check running at submission.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Client records and fee terms. Keep each client company, its hiring contacts, the fee basis agreed, payment days and the replacement window on one record.
  • Mandates and job orders. Record every requirement with the job description, seat count, location, salary band, priority and closing date against the client who raised it.
  • Candidate database. Hold candidate profiles with their CVs, current role, notice period, expectation, skills and every mandate the person was considered for. Recruiters look a candidate up by skill, role, location or notice period.
  • CV sourcing and intake. Add CVs from mail, portal downloads, referrals and walk-ins, catch duplicates on phone or mail, and tag each one to a mandate.

Operational bottlenecks to check

The same résumé goes twice

Two recruiters submit one candidate to the same client, and the client notices before either of them does. Your credibility takes the hit.

Client feedback never comes back

Candidates sit after the first or second round with nobody chasing the panel. A good profile goes cold. The mandate stays open.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Mandate taken

    A client sends a requirement. The role, seat count, location, salary band, fee basis and closing date are recorded against that client company.

  2. 2. Sourcing

    Recruiters pull CVs from the database, portals, referrals and walk-ins. Every CV attaches to a candidate record. Tagging then links it to the mandate it answers.

  3. 3. Screening

    The recruiter calls the candidate and notes current role, notice period and expectation. A rating against the mandate decides who enters the shortlist.

  4. 4. Submission and interview

    Shortlisted profiles go to the client with a submission date. Rounds are booked with the panel, and each verdict is written on the candidate’s row.

  5. 5. Offer and joining

    The offer, the joining date and the documents collected are recorded. Notice period and the day the candidate reports are followed until joining is confirmed.

  6. 6. Invoice and replacement window

    The fee is invoiced on the trigger agreed with that client. The replacement clock starts at joining, and collection follow-up sits with accounts.

Industry reports to connect with

  • Open mandates by client, recruiter and age
  • Pipeline count at sourced, screened, submitted, interviewed and offered
  • Closures made, offers declined and backouts before joining
  • Candidate sources that end in a placement

Questions before implementation.

When should recruitment agencies consider interview scheduling?

Use when interviews involve several participants or rounds. An application is ready for interview.

What should we bring to the requirements discussion?

Bring anonymised examples of Candidate contacts; Panel availability; Round requirements. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Arrange interview rounds around candidate and panel availability. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Calendar and messaging connections depend on agreed systems and permissions.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Interviewers are not double-booked. Use this check when reviewing the first working version.

Talk to us

Discuss interview scheduling for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements