Most scheduling arguments between an operator and a subcontractor come down to one word: 'booked'. The office thinks the plasterer is booked for Wednesday. The plasterer thinks they said Wednesday might work. The client has already been told Wednesday. Here is the short answer to the problem: scope, proposed date and confirmed booking are three separate decisions. Different people make them, at different times, based on different information. If you treat them as one, your subcontractor scheduling will keep failing in ways that are hard to trace. In this article, an operator means the contractor business that manages the client relationship, runs delivery and coordinates subcontractors and in-house operatives. You are the party that has to keep those three decisions apart.
Why the three decisions get merged
They usually merge by accident. Nobody sets out to book a trade against a scope that isn't agreed, but a busy week creates shortcuts:
- A date mentioned on a phone call becomes a booking in someone's head, and it never gets confirmed in writing.
- The scope a subcontractor prices is the client's original enquiry, not the version agreed after the survey.
- A subcontractor's price gets treated as acceptance of the job, when all it shows is that they're interested.
- Someone in the office updates the client with a proposed date because the client keeps asking.
Each shortcut saves a few minutes and costs you a return visit, a disputed invoice or an awkward call with the client. Get the order right and most of these problems don't happen.
Decision one: scope
Don't propose a date until the scope is settled, because the scope is what tells you how long the work takes, what has to happen before it and who needs to be on site.
What the scope needs to settle
For each piece of subcontracted work, write down:
- The exact work included, in plain terms a tradesperson would recognise.
- What is excluded, especially the grey areas like making good, disposal and minor adjacent repairs.
- Who supplies materials, and when they will be on site.
- Access arrangements, including keys, parking, occupied rooms and working hours.
- What finished looks like, and what evidence you want back, such as photos, test results or certificates required under current regulations for that trade.
Who makes the scope decision
You agree the scope with the client, and the subcontractor confirms they can deliver it and prices it. Until both of those have happened, a price is only an estimate for whatever the subcontractor imagined the job to be. If the scope moves after pricing, go back and reprice. Don't assume the old figure still stands.
One practical point: in some workflows a subcontractor can price before your vetting of them is complete. That's fine as long as everyone understands that a price is not an award. Run your checks and give approval at the stage where you actually commit the work.
Decision two: proposed date
A proposed date is a suggestion, not a commitment. It says, 'this is when I could do it, if the conditions are right.' Operators get into trouble when they record it as though it were a booking.
Before a proposed date can become anything firmer, check it against what surrounds it:
- Has the preceding work finished, or will it have finished by then?
- Will the materials be on site?
- Is access confirmed with the client or occupier?
- For external work, is there a realistic weather allowance?
- Does anything need inspecting or signing off before the next trade covers it up?
Illustrative scenario: when proposed dates don't line up
This is a fictional example for illustration. An operator is refurbishing a kitchen in a rented flat. In-house operatives are handling the strip-out. An electrician subcontractor is doing first fix, a plasterer comes next, then a kitchen fitter. The electrician proposes Tuesday. The plasterer proposes Wednesday. On paper, that looks tidy.
But the first fix has to be checked before the walls are closed up, and the electrician says the check might not happen until Wednesday morning. If the office had treated both proposals as bookings, the plasterer would turn up to walls that can't be covered yet. Because the dates are held as proposals, the operator can ask the plasterer whether Thursday works, confirm the electrician for Tuesday, and only then fix the plastering day.
Sequencing is the operator's job. The proposed dates tell you what is possible. You still have to decide what order the work happens in.
Decision three: confirmed booking
A confirmed booking is the point where both sides have committed. In practice that means you and the subcontractor have agreed, in writing:
- The date and arrival window.
- The version of the scope they are working to.
- The agreed price for that scope.
- Access and any site rules.
- Who to contact on the day if something changes.
The operator confirms the booking, not the subcontractor and not the client. Once it's confirmed, update the client with a date you're prepared to stand behind. If you tell the client any sooner, you're passing on a guess.
How this works in Plan@Job
Plan@Job is AI-powered project and operations management for construction and property businesses, and its project plan is designed around separating the work in this way.
Stages hold scope, dates, status and costs
In Plan@Job you split a job into internal stages. Each stage carries its own scope, dates, status and costs, and a stage can be delivered by a subcontractor or by your in-house operatives. In the kitchen example, strip-out, first fix, plastering and fitting would each be a separate stage. Keep each stage's status accurate: don't move it on until the booking is actually confirmed.
The client sees the overall agreed scope and price, plus whatever evidence you choose to share. Internal stage costs and the identity of your subcontractors stay internal. So the back-and-forth over proposed dates between you and your trades doesn't reach the client before you're ready.
One thing to be clear about: Plan@Job doesn't calculate critical paths or schedule dependencies automatically. You decide the sequence. The stages just give you somewhere accurate to record it.
Follow-ups without handing over the decision
Daniel Reed, Plan@Job's AI Operations Manager, helps with the chasing that usually slows this process down. He supports follow-ups on outstanding quotes and proposed dates, and he produces a morning brief so you start the day knowing what still needs answering. You can read more about how the AI staff work.
Daniel doesn't award work, set prices or confirm bookings for you. He keeps things moving, and the commitments remain your decision.
What needs a person's decision
Even with good tools, these points need someone in your business to sign them off:
- Agreeing the scope with the client, and agreeing any variations.
- Accepting a subcontractor's price and awarding the work.
- Sequencing stages where one trade depends on another.
- Turning a proposed date into a confirmed booking.
- Telling the client a date.
If you can't name who owns each of these in your business, fix that before you fix anything else.
When scope changes after booking
Variations are where the separation pays off. If the client adds work after a booking is confirmed, you're back at decision one. Agree the new scope, get it repriced, check whether the proposed date still works and then reconfirm. Don't just add the extra work to an existing booking and hope the subcontractor absorbs it. That's how price disputes start on the day the invoice arrives.
If you want to compare notes with other UK firms on how they handle variations and trade sequencing, the Contractor Club community is a good place to ask.
Putting it into practice
Start with your next job, not your whole book of work. Break it into stages, write the scope for each one before you ask anyone for a date, and don't change a stage's status until the booking is confirmed in writing. See how stages, dates and costs fit together on the Plan@Job project management page. When you're ready to try it on a live job, create an operator account.
FAQ
Should I give the client a date before the subcontractor confirms?
It's better not to. If the client needs something, give them a window and say clearly that it's provisional. Only give a firm date once the booking is confirmed, so the only dates you commit to are ones you can deliver.
Can a subcontractor quote before they are fully vetted?
In some supported workflows, yes. A subcontractor can price before your vetting is complete. What matters is that you finish your checks and approve them before you award the work, and that nobody treats the price as confirmation that the job is theirs.
Does Plan@Job schedule stages automatically?
No. Plan@Job lets you record each stage's scope, dates, status and costs, and Daniel Reed helps with follow-ups on quotes and proposed dates. The operator still sequences the stages and confirms the bookings.
Published 30 September 2026.