The requisition is the record
Client, role, rates, hours and cover requirements captured once, then worked through the pipeline.
A staffing agency placing 300 workers across 14 client sites, invoicing weekly, and rebuilding every invoice by hand from timesheets chased by email.
This is a worked example built from the real product, not a testimonial from a named customer. Figures show what the workflow removes, and the maths behind them is stated on the page. We would rather show you an honest model than invent a case study.
Requisitions arrived by email and were tracked in a spreadsheet. Candidate compliance lived in a folder. Timesheets were paper or PDF, emailed by site managers when chased, and typed into a second spreadsheet.
On Friday, someone rebuilt every client invoice from those typed hours, applying charge rates from a rate card that existed in two versions. Disputes were common, because the client had never formally agreed the hours being billed.
Margin was known in aggregate at month end, and never at the moment a consultant agreed a rate.
Client, role, rates, hours and cover requirements captured once, then worked through the pipeline.
A placed worker gets real shifts and clocks in on the client’s site inside a geofence.
The site contact approves timesheets in their own portal — the person who was actually there.
Approved hours plus charge rates equal the invoice. Nothing is re-keyed and nothing is in dispute.
Requisitions, candidates and placements sit on one board with compliance attached to every worker, so nobody is submitted whose DBS or right to work has lapsed. Fill rate and time-to-fill become measured facts per client.
Your client sees their own cover, approves their own hours and downloads their own invoices, scoped strictly to their sites. When the invoice arrives it references hours they signed for themselves.
Stated openly so you can check them against your own operation rather than take them on trust.
| Task | Before | After | Saved |
|---|---|---|---|
| Chasing and typing up timesheets | 6.0 h/wk | 0.5 h/wk | 5.5 h/wk |
| Rebuilding invoices from typed hours | 4.0 h/wk | 0.5 h/wk | 3.5 h/wk |
| Resolving invoice queries and credits | 3.0 h/wk | 0.5 h/wk | 2.5 h/wk |
| Checking worker compliance before submission | 2.0 h/wk | 0.25 h/wk | 1.75 h/wk |
| Weekly total | 15.0 h | 1.75 h | 13.25 h |
Modelled on the workflow described above. Your operation will differ — the point is which tasks disappear, not the exact figure.
It works best when they do, because approval by the person on site is what removes the disputes. Where a client will not, hours can still be approved internally and invoiced the same way.
TaskBit pays workers you pay directly and exports approved hours for everything else. It is not an HMRC-recognised filer — see payroll.
Yes, through vendor pools: the partner coordinates their own workers and sees only their assignments.
The agency features — clients, requisitions, placements and invoicing — are on Pro.
Start free, or book a demo and we will build your rota into it first.
No credit card. Cancel any time. Or book a demo instead.