PAYE and umbrella placements are different things

A driver is placed. Someone ticks "placed" in the CRM, or adds a row to the spreadsheet, and moves on. Later, payroll asks which route this was. Finance asks why the margin looks wrong. The client asks for a timesheet format that matches how they buy cover. The answer is buried in a note someone typed under pressure: "umbrella — chase invoice."

That note is doing the work of a data model. It should not have to.

For UK HGV and industrial agencies, PAYE and umbrella placements are everyday commercial reality. Treating them as the same "placement" with a free-text comment is how errors creep into billing, reporting, and the Monday-morning scramble to explain what actually went out last week.

Same driver. Different commercial object.

On the desk, both routes put a person on a client's job. That is where the similarity ends.

PAYE means the agency is employing the worker for that engagement — tax, NI, and the payroll path that follows. Umbrella means a different company sits between worker and agency, with its own invoice trail, margin shape, and paperwork habits. The compliance questions for the driver may look similar. The money, the documents, and the reporting do not.

When your system only knows "placement", every downstream step becomes archaeology. Who invoiced whom? Was this on our payroll or theirs? Why does this week's margin report mix two kinds of deal as if they were identical? People who know the desk can answer from memory. Systems that only store a single placement type cannot.

Generic CRMs make this easy to get wrong. They give you one object called Opportunity, Placement, or Job Fill, plus a notes field. Consultants add a drop-down. Someone forgets to set it. Someone sets it after the fact. Someone uses "other" because the list never matched how your clients actually buy. The real commercial detail slides back into email and Excel — the same places compliance already hides when the worker record is too thin.

Why the comment field is not enough

A comment is fine for context. It is a poor primary key for how you run the business.

You cannot sort a board by comment. You cannot filter "who is out this week on PAYE" without reading every row. You cannot hand a clean extract to payroll or accounts without someone re-classifying placements by hand. Under pressure, the comment gets skipped, abbreviated, or written in a shorthand only one consultant understands.

That is not a people problem. It is what happens when the product treats commercial structure as optional decoration.

Licence categories show the same pattern on the compliance side: generic candidate tags are not Class 1, Class 2, and the rest of what a job actually needs. PAYE versus umbrella is the commercial twin of that mistake. If the desk thinks in two placement shapes, the software should too — not after a change request, and not only in a process note taped to a monitor.

What the pipeline needs to know

A placement sits at the end of a chain that already has meaning: a candidate becomes a worker, a compliant worker becomes available, a client's job needs covering, scheduling matches person to shift. Nothing useful should be typed in twice.

That chain only stays honest if the placement itself carries the commercial type. Otherwise you rebuild it every time finance, payroll, or a client report asks a basic question. Worker compliance can be perfect and the desk still loses an afternoon reconciling which engagements were PAYE and which were umbrella because the board never distinguished them.

Haulbase is being built so PAYE and umbrella placements are handled as the different things they are — first-class in the product, not a comment bolted on because a generic CRM only had one placement shape. Same principle as licence categories on the worker, clients kept separate from candidates, and jobs linked to the company that raised them. The detail generic software misses is rarely glamorous. It is the difference between a system that mirrors how the agency thinks and one you constantly translate into.

Honest about launch, clear about the point

At launch Haulbase includes the job board through registration, worker, client, and job management, plus scheduling and placement tracking. DVLA and Right to Work status are tracked manually on the worker, with documents in one place. Automated DVLA checks, automated Right to Work verification, and payroll or umbrella company integrations come later.

That last point matters for this topic. Distinguishing PAYE from umbrella in the placement record is not the same as live payroll feeds or umbrella API connections on day one. We would rather ship a desk that already treats the two routes as different commercial objects than pretend the integrations are finished when they are not. The foundation is the model. The integrations follow.

Built with real agency back-office experience — the kind that has watched a "simple" placement note turn into a week of margin arguments — not a consultant's best guess after renaming fields on a blank CRM.

Two routes, one board that tells the truth

Drivers will still move between PAYE and umbrella depending on the engagement. Clients will still buy cover in the way that suits them. What you should not need is a scavenger hunt through comments every time someone asks which route last week's shifts actually took.

If your placement board still treats both as the same tick-box, you're the reason we're building Haulbase.