If you are a main contractor, a project progress update from an operator should let you answer three questions without picking up the phone. Is the package on track against what was agreed? What happens next, and when? Is anything waiting on you? By operator we mean the contractor business you have commissioned to deliver a package, which manages its own clients, subcontractors and in-house operatives. Photos, percentages and site diaries are only useful in an update if they help answer those three questions. This guide covers what to ask for, what you should not expect to see, and how the workflow runs in Plan@Job.
Why so many operator updates miss the mark
Most package managers have had all three of the usual bad updates: forty unlabelled photos on WhatsApp, a Friday email saying "all going well", or a long diary of who was on site each day. Each one takes some effort from the operator, and none of them tells you where the package stands against the scope you agreed.
The effect builds up. You can't tell "started" from "nearly finished", so you chase. Your own client meeting or programme review comes round and you're piecing it together from phone calls. Then a variation that was agreed verbally on site turns up at valuation as a surprise.
The fix is usually not more effort from the operator. It is agreeing the shape of the update at kick-off and keeping to it.
The six things a useful project progress update covers
1. Status against the agreed scope
Status should be reported against the scope items you contracted for, not the operator's internal task list. "Level 1 partitions complete, level 2 ceilings about half boarded, decoration not started" is useful. "Good progress this week" is not.
A simple status for each scope item is enough: not started, in progress, complete, or snagging. If the operator has split the work into its own internal stages, that is fine, but the update you receive should go back to your scope.
2. Evidence you can check
Photos are evidence only if you can tell what they show. Ask for photos that are dated, linked to a scope item, and wide enough to show the location as well as the detail. Where the work needs them, ask for test results, certificates or a completion report alongside.
Good evidence protects both sides. It supports the operator at valuation, and it gives you something solid to pass up the chain to your own client.
3. Next dates and what they depend on
An update should say what starts or finishes next and when, plus what has to be true first. That might be access to a floor, a delivery, another trade finishing, or a design answer. Dependencies written in plain words ("ceilings start Tuesday once M&E first fix in the corridor is signed off") are worth more than a percentage.
4. Blockers and decisions waiting on you
This is often the most valuable line in the whole update, and the one most often left out. Ask the operator to list anything they are waiting on from you, such as drawings, access, a client choice of finish, or an answer to a technical query, with the date they need it by. If you can see this early, you can sort it before it turns into a delay claim.
5. Changes and their effect
Every change should appear in writing. That means what changed, who instructed it, the likely effect on time and price, and whether it is proposed or agreed. A variation that only exists as a conversation on site will cause an argument later.
6. Safety and handover items
As principal contractor you will have your own arrangements under the Construction (Design and Management) Regulations 2015. The operator's update should flag incidents or near misses, any change in method or risk assessment, and which handover documents are still outstanding. Leaving these to the final week is a common reason handover slips.
What you should not expect to see
You will not normally see the operator's internal stage costs, margins or which subcontractor is doing which stage. Those are the operator's commercial matters, in the same way you would not show your client your subcontract prices.
Plan@Job is built around that split. The client view shows the overall agreed scope, the agreed price and the evidence the operator chooses to share. Internal stage costs and subcontractor identity stay with the operator. If your contract requires you to approve who works on your site, deal with that through the contract terms and your site induction process, not the progress screen.
How the workflow runs in Plan@Job
On the operator's side, the job is split into internal stages, each with its own scope, dates, status and costs. Each stage can be delivered by a subcontractor or by the operator's in-house operatives, and the operator updates status as the work moves. You can read more about how stages work on the project management feature page.
Operators can also use Daniel Reed, Plan@Job's AI Operations Manager. He supports them with quote follow-ups, proposed-date follow-ups and a morning brief, which makes it more likely a stale date gets chased before it reaches you. Daniel doesn't award work, set prices or commit anyone to anything. Those decisions stay with people at the operator. The AI staff page explains what each AI colleague does and doesn't do.
On your side, jobs reach your main-contractor portal through job links the operator shares or that you request and save. Access across your team is based on membership, so a package manager and a quantity surveyor can both see the same job without forwarding emails. For each job you see the overall agreed scope and price and the evidence the operator has shared.
One point to be clear on: opening a Plan@Job account does not come with an operator. The service is agreed directly between you and the operator you commission.
Plan@Job also does not build a critical path or schedule dependencies for you. Stage dates and status are set by the operator, and dependencies are stated by people. Your master programme stays wherever you already run it.
An illustrative weekly update
Illustrative example. The companies, site and details are fictional.
A main contractor is fitting out a ground-floor clinic in Nottingham. It has commissioned an operator to deliver partitions, ceilings and decoration. The Thursday update reads:
- Status: treatment room partitions complete. Corridor partitions in progress, due to finish Monday. Ceilings and decoration not started.
- Evidence: dated photos of each completed treatment room, taken from the doorway and close up at the head track detail.
- Next: ceilings start Tuesday, once the main contractor confirms the corridor M&E first fix is signed off.
- Waiting on you: confirmation of the door ironmongery schedule by next Wednesday, or the frame order will slip.
- Changes: one proposed variation for an extra acoustic partition in consult room 3, with price and time effect to follow for your approval. Not yet agreed.
- Safety and handover: no incidents. Fire-stopping records for completed walls attached. Product data sheets for the ceiling system still to come.
The package manager can read that in two minutes and knows exactly what to do: chase the M&E sign-off and the ironmongery schedule.
Agree the format at kick-off
Requests made halfway through a job feel like criticism. Asked for at the start, they are just how the job runs. At the pre-start meeting, agree:
- The day and time updates arrive, and the format they come in.
- The scope list to use as headings, taken from the subcontract.
- The evidence standard, meaning what photos show and which documents go with which scope items.
- Who on your side receives updates and who answers blockers, with a realistic response time.
- How variations are raised, priced and approved before work starts.
- What triggers an out-of-cycle update, such as an incident, a slipped key date or a design clash.
It is also worth sharing your own reporting dates, so the operator knows when you need information to brief your client.
What still needs a person's decision
Software can organise the information, but it doesn't sign anything off. People still need to:
- approve or reject variations and their price,
- accept completion and close out snags,
- make valuation and payment decisions under your subcontract,
- make safety calls on site.
If you'd like operator updates to arrive in a consistent, evidence-backed shape, see how the Plan@Job main-contractor portal works for UK main contractors.
FAQ
How often should an operator send a project progress update?
Weekly suits most packages, with an extra update for incidents, slipped key dates or design clashes. On short, intensive phases such as a weekend shutdown, a daily update may make more sense. Agree the frequency at kick-off rather than adjusting it as you go.
Can I see which subcontractors the operator is using?
Not through the Plan@Job client view. Subcontractor identity and internal stage costs stay with the operator. If you need to approve who works on your site, set that out in the subcontract and manage it through your induction and site access process.
Does Plan@Job create the programme or critical path for the package?
No. The operator sets the dates and status for each internal stage, and dependencies are written down by people. Plan@Job doesn't calculate a critical path or schedule dependencies, so keep your master programme in the tool you already use.