Work
Mandates and the work against them
Each mandate is work with a client, a specification, a fee basis, an owner, a stage, an age and the effort recorded against it.
Why it matters here The mandate is the unit that either converts or does not, and effort against it is the only way to tell which is which.
In practice Fourteen mandates with no submission in three weeks, ranked by the consultant hours they have consumed.
Relationships
Candidates, clients and hiring managers
Candidates and clients are records with their history, submissions, interviews, feedback, placements and preferences.
Why it matters here The candidate database is the agency’s asset, and it is worthless if it is personal to a consultant.
In practice A candidate submitted for three roles across two years, with every piece of feedback on their record.
Workflows
Submissions, interviews and offers
Each stage is a defined step with an owner, a date and an age, from submission through interview rounds to offer and acceptance.
Why it matters here Recruitment is a stage business, and every loss happens at a specific stage that can be measured.
In practice Thirty-one submissions with no client feedback in ten days, chased on a schedule.
People
Consultants, researchers and account managers
The team is modelled once, and every mandate, submission and placement shows who owns it.
Why it matters here A desk is a person, and the agency needs to see what each desk is carrying and converting.
In practice Submissions per mandate and interview-to-offer conversion by consultant.
Records
CVs, notes, contracts and terms
Documents and interview notes attach to the candidate, mandate or placement they belong to.
Why it matters here Terms of business and fee agreements decide what is billable, and they surface in disputes months later.
In practice The signed terms and the agreed fee percentage on the client record, referenced at invoicing.
Communication
Feedback and candidate contact
Notes, reminders and activity attach to the candidate, mandate or submission they concern.
Why it matters here A candidate’s reason for declining is the most useful information the agency will get that week, and it usually stays in a phone.
In practice A candidate’s salary expectation recorded on their record, visible for the next relevant role.
Reports and analytics
Pipeline and conversion reporting
Mandate conversion, time-to-submit, submission-to-interview and interview-to-offer rates, client feedback speed, guarantee exposure and consultant performance come from the operational records.
Why it matters here Agencies measure placements and almost nothing else, which means they cannot tell a bad month from a bad mandate mix.
In practice Fill rate by client, which frequently changes which mandates the agency should accept.
Verity AI
Ask the desk a question
Verity AI answers from your own mandate, candidate, submission and placement records, respects permissions, and can create assigned follow-ups.
Why it matters here The valuable questions are about silence and about effort with nothing to show for it.
In practice "Which submissions have had no feedback in ten days?" returns thirty-one, with chases assigned by client.
Control
Who can see which candidates
One permission model and one audit trail across every record.
Why it matters here Candidate data is personal information and consultants compete internally, so access needs to be deliberate.
In practice Consultants see their own desks and the shared candidate pool; every access is on the trail.
Locations
Desks, teams and offices
Organisational units roll into the agency, with permissions and reporting following the same structure.
Why it matters here Multi-desk agencies only learn from comparison if every desk records the same stages.
In practice Conversion by stage across desks and offices.