Contract Staffing

How is contract staffing different from a statement of work?

Under contract staffing the client buys time and capacity, directs the day-to-day work, and pays for hours. Under a statement of work the supplier commits to a defined deliverable, controls how the work is performed, and is paid against milestones or acceptance. The distinction is not cosmetic: it changes who carries delivery risk, how the arrangement is priced, and how it is characterized if the relationship is later examined. Labelling a time-and-materials arrangement as a statement of work to change its treatment is a common and risky shortcut.

What ends an assignment, and how cleanly?

Assignments end at the planned date, are extended, are cut short by the client, or end because the worker leaves. Each route has different consequences: an extension needs a rate and dates confirmed before the old assignment lapses, an early end triggers whatever notice the agreement sets, and a worker resigning mid-assignment leaves the supplier owing the client a replacement conversation. Recording which of these happened, rather than simply closing the record, is what makes assignment-end data useful later.

Where does contract staffing sit alongside other supply models?

It sits between direct hire, where the client takes on the person permanently and the supplier is paid once, and payrolling, where the client has already found the person and the supplier only employs and pays them. Temp-to-hire is contract staffing with a conversion route agreed in advance. Understanding which of these a client is actually asking for prevents a supplier from quoting one model and delivering another.

Who holds the employment relationship in contract staffing?

The defining feature is that the person working at the client site is not on the client's payroll. The supplier engages them, either as its own employee or through a subcontract, and takes on the obligations that come with that engagement: paying them on an agreed cycle, making the deductions and contributions the engagement type requires, holding the insurances the client contract specifies, and keeping the records that prove all of it happened.

Between supplier and client there is a commercial services agreement, not an employment contract. The client buys hours or a capacity commitment. This is why an assignment can end without the client running a termination process, and it is also why a client instructing the worker as though they were staff can create exposure. The precise line between acceptable direction and an employment-like relationship is set by local law and varies by country and often by state, so the arrangement should be reviewed with counsel wherever it operates.

What does a contract assignment actually specify?

A workable assignment record names the scope of work, the site or remote arrangement, the start date, an expected end date, the hours the client expects to be available, the notice each side must give, and the bill rate with any overtime or shift treatment attached. Vague assignments are where disputes start: if nobody wrote down whether travel time is billable or whether a public holiday is charged, both parties will remember it differently at invoice time.

Assignments also carry restrictions that outlive them. Non-solicitation clauses, conversion terms that apply if the client wants to take the person onto its own payroll, confidentiality obligations, and any intellectual property assignment all sit here. A supplier that does not read these before signing can find that a worker it recruited cannot be placed elsewhere in the same sector for a period, which changes the economics of the desk considerably.

How does the money move on a contract desk?

The cycle is timesheet, approval, invoice, collection, and it repeats every week or every month for the life of the assignment. The worker submits hours, an approver at the client signs them off, the supplier invoices against approved hours only, and payment arrives on the agreed terms. Every step is a place where the cycle stalls, and an unapproved timesheet is an uninvoiceable one no matter how certain everyone is that the work happened.

The strain point is that the supplier usually pays the worker before the client pays the invoice. That gap is funded out of the supplier's working capital, so the longer the payment terms and the larger the contractor headcount, the more cash is tied up in work already delivered. This is why suppliers negotiate payment terms as hard as they negotiate rates, and why a desk can be profitable on paper and still run out of money.

Why do clients choose contract over permanent hiring?

The usual reasons are timing and reversibility. A project has an end date, a permanent headcount request has not been approved, a specialist is needed for a defined piece of work, or a team needs cover for an absence. In each case the client wants capacity without adding to a permanent establishment it may not be able to unwind quickly.

The trade is continuity and accumulated knowledge. A contractor who leaves at assignment end takes context with them, and a team that runs a critical system on rolling contracts is carrying a dependency risk. Clients that use contract staffing well are explicit about which work is genuinely temporary and which has quietly become permanent work being done on a temporary arrangement, because the second case usually costs more over time than converting would have.

What does a supplier need in its systems to run contract work?

Contract work needs record-keeping that permanent placement does not. Each worker has an assignment with dates, a pay rate, a bill rate, an approver, a set of compliance documents with expiry dates, and a status that changes over time. The system has to answer questions such as which assignments end in the next month, whose right-to-work document expires soon, and which timesheets are outstanding, without anyone rebuilding a spreadsheet.

A recruiting system that only tracks candidates to a hire date does not cover this. Suppliers typically pair an applicant tracking system for the pipeline with timesheet and billing capability, and connect both so an assignment created at placement carries its rates and dates forward instead of being retyped. Where the client runs a vendor management system, the supplier ends up maintaining the same assignment in two places, which is a reconciliation job worth planning for.