Contract and interim
Submit first, price the margin, and never miss an extension
On a contingent desk you are paid for being first with a viable candidate, and you keep being paid only for as long as the assignment keeps renewing.
Surhires supports a contingent contract desk end to end: a shortlist assembled and submitted within the hour, pay rate and charge rate held on the placement so margin is visible, extension dates tracked as their own events, and contractor documents monitored for expiry through the assignment.
By Surhires Editorial · Published · Reviewed
The money question is margin per contractor per week, multiplied by weeks
A permanent fee is a single event. Contract revenue is an annuity: a margin between what you pay the contractor and what you charge the client, earned every week the assignment runs. That changes what a good week looks like. Two new placements at a thin margin on eight-week assignments are worth less than one extension of a strong-margin contractor for another six months, and a desk that only celebrates new starts will keep making that trade without noticing.
So the desk needs three numbers visible at all times: how many contractors are on assignment, what the blended margin is, and which assignments end inside the next sixty days. Surhires computes all three from the placement records themselves, which means nobody is maintaining them in a spreadsheet and nobody is arguing about which version is current.
When four agencies hold the same role, submittal speed is the product
Contingent means you are paid on success and you are not the only one trying. A client releases a requirement to a panel at nine in the morning and a hiring manager who is already busy will look seriously at the first two or three profiles that arrive and skim the rest. The candidate quality difference between agency one and agency four is usually smaller than the attention difference.
That makes the hour after intake the most valuable hour on the desk, and almost all of it is normally lost to mechanics: searching, formatting a CV to the client's template, writing a summary, finding the right contact, attaching the rate. Surhires removes the mechanics. The sourcing agent searches your own database against the brief first and returns candidates who already match, formatted profiles are generated to your template rather than rebuilt in a word processor, and a submittal is a record you create in one action with candidate, contact, requisition, documents and rate attached.
- Job intake turns a client email or brief into a structured requisition with must-haves, rate band and stages
- Database-first sourcing surfaces contractors you already know before you pay for new sourcing
- Formatted candidate profiles generated to a per-client template, with contact details masked where required
- Submittal timestamps recorded, so submittal-to-response time per client becomes a real number
Pay rate and charge rate belong on the placement, not in a side calculation
The most common way a contract desk loses money is not a bad placement. It is a placement whose economics nobody looked at closely because the two rates lived in different places: the charge rate in the client agreement, the pay rate in a message thread with the contractor, and the margin in a recruiter's head.
A contract placement in Surhires carries pay rate, charge rate, the unit both are quoted in, the currency, the assignment start and end dates, and any agreed uplift for overtime. Margin is derived rather than typed. Because it is derived, it can be reported: margin by client, by recruiter, by role type, and against the desk's own average. A recruiter about to agree a rate can see where it sits before they agree it rather than after the invoice.
Rates can also be versioned within an assignment. A contractor who negotiates an increase at extension does not overwrite the history, so the placement shows what was earned across each period rather than only what is true today.
Extensions are where a contract book compounds or quietly leaks
Every contract placement has an end date, and every end date is a decision that somebody has to make before it arrives. If the conversation happens in week ten of a twelve-week assignment, the extension is usually straightforward. If it happens in week twelve, the contractor has already taken a call from somebody else, and if it happens in week thirteen, the assignment has ended and the revenue with it.
Surhires tracks the extension as its own object rather than as an edit to the end date. Each assignment shows the current end, the notice terms, the extension history and a countdown, and the desk gets a task at a lead time you set. Extensions are visible on the same pipeline the desk already works, so a book of two hundred contractors does not need a separate tracker to stay honest.
The reporting consequence matters as much as the reminder. A desk can see its extension rate by client and by recruiter, which is a much better predictor of next quarter's revenue than new-placement volume is.
- Extension events with their own start, end, rate and approver, kept as history rather than overwriting
- Configurable lead time before each end date, raised as a task on the owning recruiter
- Assignments ending in the next thirty, sixty and ninety days as a standing view
- Extension rate by client and recruiter, reported from actual outcomes
Contractor documents have to stay current through the assignment, not just at onboarding
Onboarding compliance is the easy half. A contractor starts with a right-to-work document, an insurance certificate, a background check, an NDA, a signed schedule and whatever else the client requires. Six months into a twelve-month assignment, the professional indemnity certificate expires, the visa approaches its end date, and the background check passes the client's stated validity window.
Documents are typed records on the contractor and on the assignment, each with an issue date, an expiry date and the file. Expiry generates a reminder at a lead time you configure, and a document required by a specific client can be marked as such so the requirement travels with the assignment rather than living in one recruiter's memory. Where an IR35 or worker-status determination applies, the status flag and the determination record sit on the placement.
None of this is a compliance guarantee and the page will not pretend otherwise. The product captures documents, stores determinations and reminds you before dates pass. Deciding what is required, verifying it and standing behind it remain yours.
An assignment ending is a sourcing event, not an administrative one
The contractor finishing on Friday is the best-qualified person on your database for a similar role starting Monday. They are proven, they are known to you, they are available on a date you can predict, and they cost nothing to source. On most desks this is handled by whoever happens to remember.
Redeployment in Surhires works from availability dates. Every contractor on assignment has a known end date, so a search for a role starting in three weeks can include people who are technically still working. Contractors approaching an end date without a confirmed extension appear on a redeployment view, and their skills, rate history and client history are already structured for matching.
The same data drives the honest version of a contractor pool: not a tag someone applied in 2024, but people whose last assignment ended recently, whose rate expectation is recorded, and whose availability is a date rather than a guess.
What the owner needs to see on a Monday morning
The Placement Pipeline Command Centre shows submittals out by client and by recruiter, interviews booked and slipped, offers live, placements closed and revenue booked against revenue invoiced. On a contract desk the two panels that earn their place are contractors currently on assignment and assignments approaching their end date.
Recruiter performance is measured on the things a contingent desk actually controls: submittals sent, submittal-to-interview conversion by client, time from intake to first submittal, and extension rate. Placement volume alone rewards the recruiter who starts the most contractors, not the one who keeps them running.
Where Surhires stops on a contract desk
Surhires raises the placement record and the first invoice. It is not a back-office system: it does not run contractor self-billing, timesheet approval, weekly pay cycles, or the reconciliation between what a client was invoiced and what a contractor was paid. Those belong in a pay-and-bill or accounting system, and integrations with QuickBooks and Xero exist to move the invoice across.
It is also not an employer of record. Where you need a legal employer for a contractor in a country you have no entity in, that is a partner relationship, and the product's job is to hold the placement data cleanly so the handover to that partner is not a re-keying exercise.
What you get
Structured job intake
A client brief or forwarded email becomes a requisition with must-haves, rate band and stages.
Database-first sourcing
Contractors you already know surfaced against the brief before new sourcing spend.
Templated profile formatting
Client-specific CV templates generated from the record, with details masked where required.
Submittal records
Candidate, contact, requisition, documents and rate captured as one timestamped object.
Submittal speed reporting
Time from intake to first submittal, and submittal-to-response, measured per client.
Pay and charge rates
Both rates, units and currency held on the placement with margin derived, not typed.
Rate versioning
Rate changes at extension recorded as periods, so historic margin stays accurate.
Extension events
Each renewal carries its own dates, rate and approver rather than overwriting the last.
End-date countdowns
Configurable lead-time tasks before every assignment end, on the owning recruiter.
Redeployment view
Contractors approaching an end date with no confirmed extension, ready to match.
Document expiry tracking
Insurance, right-to-work and check documents with expiry dates and advance reminders.
Client document requirements
Per-client required documents attached to the assignment rather than held in memory.
Worker status flags
IR35 and worker-status determinations recorded against the placement with their date.
Margin reporting
Blended and per-placement margin by client, recruiter and role type.
Invoice handoff
Placement invoicing raised in product and exported to QuickBooks or Xero.
Questions recruiters ask
Can the same candidate be in play on several contract roles at once?
Yes, and it is modelled properly rather than duplicated. A candidate can hold submittals against multiple requisitions with independent stages and rates, and the pipeline shows both sides of the many-to-many relationship. General CRMs that model a single deal object break exactly here, which is why contract desks abandon them.
Does Surhires handle timesheets, self-billing and contractor pay?
No. It raises the placement and the first invoice, and integrates with QuickBooks and Xero. Timesheet capture, approval workflows, weekly pay runs and the reconciliation between client invoicing and contractor payment belong in a pay-and-bill system. We would rather name that boundary than sell you a half-built back office.
How are extensions handled if the rate changes?
The extension is a separate record carrying its own start, end, pay rate and charge rate, so the placement holds a history of periods rather than a single current rate. Margin reporting reads the periods, which means a report covering last quarter uses last quarter's rates rather than today's.
Can we stop a submittal going out if a required document is missing?
Yes. Required-at-stage rules block a stage transition until the named fields or documents are present. Which documents are required is configured per client or per job type, so a public-sector client that insists on a check before submittal is enforced by the workflow rather than by a recruiter remembering.
Does the product make an IR35 or worker-status determination for us?
No. It records the determination you made, who made it, when, and the reasoning attached to the placement, and it keeps that record available if the position is questioned later. The determination itself is a judgement about the engagement that sits with you and your client, not with software.
How do we see whether a client is actually worth working?
Client relationship scoring uses real signals: requisitions released to you, submittals sent, submittal-to-interview conversion, time to respond, placements made, extension rate and margin. A client who releases a lot of roles and converts almost none of them shows up as a cost rather than as activity.
Keep reading
- A pipeline that tells you what is slipping
- Invoice the placement you already recorded
- A client portal your hiring managers will actually open
- Applicant tracking built for a billing desk
- Catch a client going quiet before the reqs stop
- Numbers a desk can act on before Friday
- Run a contract book on margin, not on fee
See it against your own reqs
Bring one live role and three resumes. In twenty minutes you will see the match scores, the shortlist and the placement invoice that comes out the other end.