Job Posting for Recruitment agencies
Maintain approved vacancies and their advertising status.
Does this function belong in your operation?
Use when vacancies require approval or appear across several channels.
A manager requests a new or replacement role.
A mandate’s job description goes to the agency’s own careers page and to chosen job portals, with one reference code. Applicants land under that mandate. Closed roles come down together.
Bring the records the workflow depends on.
- Role description
- Headcount approval
- Advertising channels
Outputs to check
- Approved vacancy record
- Channel publication register
- Open and closed vacancy list
Follow the job posting workflow.
Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.
Who uses the module, and who approves?
Keep responsibilities distinct even when one person holds more than one role.
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.
Can this work independently?
Vacancies can be maintained independently, with applications entered or imported later. Website or external job-board publishing is a separate connection with its own permissions. Closing the internal vacancy should trigger a check that published copies have also been withdrawn.
Systems and records it connects with
- Your careers page: Published vacancies and permitted application submissions.
- Resume management: Candidate profiles and original CV references.
- Candidate tracking: Application identifiers, recruitment stages and hiring outcomes.
- WhatsApp: Permitted message content and channel delivery responses.
Configure, test and introduce the workflow.
- Describe how a vacancy starts today. We write back the approval steps and the channels you use.
- You supply role templates and branch names. A careers page arrives on your own site for you to try. The owner chooses who approves openings. You get a screen where a manager raises a vacancy and approval is recorded.
- HR posts a real vacancy and watches applications arrive. The group leaves trained, with changes noted.
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.
- Unapproved roles remain unpublished.
- Applications retain vacancy references.
- Closed roles are identifiable.
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.
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. 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. 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. 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. 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. 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. 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 job posting?
Use when vacancies require approval or appear across several channels. A manager requests a new or replacement role.
What should we bring to the requirements discussion?
Bring anonymised examples of Role description; Headcount approval; Advertising channels. 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. Maintain approved vacancies and their advertising status. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.
What is outside this module?
External publishing depends on each channel's supported connection and account access.
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. Unapproved roles remain unpublished. Use this check when reviewing the first working version.
Related functions for recruitment agencies.
Discuss job posting 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
- We review your brief and the systems you already use.
- We clarify the workflow, missing information and the work to consider first.
- The proposed scope sets out the deliverables, responsibilities and dependencies.
- 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