Skip to main content
GullySystem
Professional services

Candidates Tracking for Recruitment agencies

Track each application through recruitment stages.

Applicant Tracking

Does this function belong in your operation?

Use when applications pass through several people or decision stages.

A candidate applies for an open vacancy.

Candidates move from sourced to submitted, interviewed, offered and joined, and each stage is dated against the client’s mandate. The recruiter sees who is stuck after an offer. Notice period and counter offers are noted.

Bring the records the workflow depends on.

  • Vacancies
  • Applications
  • Stage definitions

Outputs to check

  • Application-stage history
  • Recruiter follow-up list
  • Hiring outcome record

Follow the candidates tracking workflow.

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

  1. 1. Register the application

    Link the candidate to a specific vacancy.

  2. 2. Assign screening

    Give the application an owner and record the initial review.

  3. 3. Track selection stages

    Keep interview, assessment and feedback references together.

  4. 4. Record the decision

    Retain the authorised offer, decline, withdrawal or hold reason.

  5. 5. Handover the outcome

    Pass accepted offers to onboarding without automatically creating active employees.

Who uses the module, and who approves?

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

HR executive

Moves candidates along, follows up the panel, and knows what to tell anyone who calls to ask.

Branch manager

Sees only the open seats in their own branch, and the people waiting on their decision.

Owner

Reviews applications, offers and actual joiners by branch, then follows up unexplained gaps.

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.

Duplicate candidate

Link related applications without deleting separate decisions for different vacancies.

Candidate withdraws

Close the application and cancel pending interviews while retaining permitted history.

Vacancy closes

Review remaining applications and record their outcomes instead of leaving them active.

Can this work independently?

Tracking can begin with manually entered applications and vacancy references. CV storage, interviews and onboarding can connect later through candidate and application identifiers. A hired status should create an onboarding handoff rather than immediately activating payroll or system access.

Systems and records it connects with

  • Resume management: Candidate profiles and original CV references.
  • Interview scheduling: Interview times, participants, attendance and round references.
  • WhatsApp: Permitted message content and channel delivery responses.
  • Recruitment and onboarding: Accepted-offer details and joining-readiness tasks.

Configure, test and introduce the workflow.

  • Describe the stages you really use and the vacancies you run. A note comes back. Stages and rejection reasons are listed in your own words.
  • Confirm what each card should hold. Then a test candidate can be moved through every stage, with you at the controls. Share the sheets or mailboxes holding current applicants. They are loaded as a trial, with unreadable ones listed.
  • HR, branch managers and interviewers each get a short session on their own view. Their remarks return as a revised screen list. New applicants enter only through the system from here. A review follows the first closed vacancy. It checks that stage dates were kept honestly.

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.

  • Applications remain distinct by vacancy.
  • Active applications have owners.
  • Stage history survives closure.
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 candidates tracking?

Use when applications pass through several people or decision stages. A candidate applies for an open vacancy.

What should we bring to the requirements discussion?

Bring anonymised examples of Vacancies; Applications; Stage definitions. 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. Track each application through recruitment stages. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

The system records decisions rather than determining suitability or hiring outcomes.

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. Applications remain distinct by vacancy. Use this check when reviewing the first working version.

Talk to us

Discuss candidates tracking 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