Skip to main content
GullySystem
Professional services

Resume Management for Recruitment agencies

Store candidate CVs with searchable role and experience details.

Applicant Tracking

Does this function belong in your operation?

Use when CVs are scattered across recruiter inboxes and folders.

A CV arrives from an approved recruitment source.

Résumés arrive from job portals, referrals and cold calls, and are parsed into searchable fields such as skills, current pay and notice period. A recruiter finds past candidates for a new mandate. Duplicate profiles are merged.

Bring the records the workflow depends on.

  • CV files
  • Recruiter search fields
  • Retention rules

Outputs to check

  • Searchable candidate profile
  • Original CV and revision history
  • Duplicate and incomplete profile list

Follow the resume management workflow.

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

  1. 1. Receive the CV

    Record its source and the candidate's permitted contact details.

  2. 2. Check identity

    Review possible duplicate profiles before creating another record.

  3. 3. Organise the evidence

    Keep the original file and searchable role or experience details.

  4. 4. Link applications

    Associate the profile with relevant vacancies without merging their decisions.

  5. 5. Maintain retention

    Handle new versions, restricted access and approved deletion actions.

Who uses the module, and who approves?

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

HR executive

Adds CVs as they arrive, corrects what was read wrong, and searches the old ones before advertising again.

Branch manager

Reads only the CVs for the hiring manager’s own vacancy and marks the ones worth calling.

Front desk

Scans or photographs what a walk-in hands over, so paper does not sit in a drawer.

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.

Unreadable file

Request a replacement and avoid filling fields with guessed details.

Multiple CV versions

Keep dates and distinguish the candidate's current version from earlier evidence.

Deletion request

Follow the approved retention process and check linked applications before removing data.

Can this work independently?

The CV library can stand alone with controlled access and retention rules. Candidate tracking uses profiles for particular applications, while interviews and onboarding consume selected details. Importing a CV does not validate qualifications or authorise a hiring decision.

Systems and records it connects with

  • Job posting: Approved vacancies and publication or closure status.
  • Candidate tracking: Application identifiers, recruitment stages and hiring outcomes.
  • Email: Authorised message dispatch and delivery-failure records.
  • WhatsApp: Permitted message content and channel delivery responses.

Configure, test and introduce the workflow.

  • List every route CVs take into the business. We write back the intake points and who handles each.
  • HR picks the tags and skills to search by. A tag list arrives for approval. Hand over past CVs. Folders, mailboxes or sheets all work, and you review a trial import in which duplicates are marked.
  • HR and branch managers search live. Access rules are checked and corrections are made.

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.

  • Duplicates are flagged.
  • Original CVs remain accessible.
  • Restricted profiles follow access rules.
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 resume management?

Use when CVs are scattered across recruiter inboxes and folders. A CV arrives from an approved recruitment source.

What should we bring to the requirements discussion?

Bring anonymised examples of CV files; Recruiter search fields; Retention rules. 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. Store candidate CVs with searchable role and experience details. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Parsing, background checks and candidate scoring are separate scope decisions.

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. Duplicates are flagged. Use this check when reviewing the first working version.

Talk to us

Discuss resume management 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