What to Confirm Before Any Job Kicks Off
Most job problems trace back to the gap between a quote being accepted and work beginning. A short checklist - written scope, payment terms, supplier briefing, internal job record - closes that gap before it costs you anything.
Most job problems do not start on site. They start in the gap between a quote being accepted and work beginning - when scope was assumed rather than confirmed, payment terms were discussed but never written down, and suppliers were ordered from but not briefed on the actual delivery date. The handover from sales to operations covers who is responsible for the job internally. The job kickoff checklist covers something different: what needs to be confirmed with and around the customer before the first hour is spent. Without it, assumptions travel into the job unopposed.
Written Acceptance, Not Just a Verbal Green Light
A phone call accepting your quote is not a confirmed scope. Neither is an email that says "great, let's proceed." Before work begins, you need something that ties the customer to the specific version of the quote they accepted: the right spec, the right price, and the right start date.
This matters most when you have issued multiple revisions. If revision three changed a material spec or added an exclusion that revision one did not include, the customer who says yes on a call may be confirming something that no longer matches what you are about to deliver. A purchase order from the customer, a signed copy of the quote, or a written reply that references the quote number and version is the minimum you need.
The exclusions matter as much as what is included. A scope that clearly states what you will not be responsible for is your first line of protection against a variation conversation that starts with "I assumed that was part of it." Getting written acceptance does not take long; recovering from an undocumented scope change takes much longer.
Payment Terms Confirmed Before Work Starts
Payment disputes almost always trace back to a schedule that existed in one person's head but was never written down. The customer thought they would pay on completion. You expected two stage payments. Nobody documented it before work started, so the conversation happens when an invoice arrives - the worst possible time to be negotiating terms.
Before the job kicks off, agree in writing: what triggers each payment, what the amount is, and who on the customer's side approves it. If the customer requires a purchase order number on your invoice, get it before you start - not when the invoice is ready to go out and it turns out their procurement team issues those separately.
A deposit before work begins is reasonable on most jobs. It also tells you something useful. A customer who resists a small deposit before any materials are ordered or any days are booked is giving you early information about how the rest of the financial relationship will go.
Get it in writing before day one
A payment schedule agreed in writing before work starts is not a sign of distrust - it removes ambiguity for both parties. The best time to agree payment terms is before either side has spent anything.
Suppliers and Sub-contractors Have Confirmed Dates
Ordering is not the same as briefing. You can place a purchase order with a supplier and still have materials arrive in the wrong week because "delivery around week three" was treated as guidance rather than a firm commitment. Before the job starts, confirm in writing that delivery dates are locked in the supplier's system, that sub-contractors have the actual start date and site access details, and that any long lead-time items have been tracked against the programme.
One UK construction estimating consultancy reports that builders can lose up to 20% more money on projects through poor cost estimating - and a significant share of those losses trace back to procurement assumptions that were never checked before work started. A material that arrives two weeks late does not just delay the job; it moves your team onto another project, pushes the programme, and creates the conditions for a variation conversation you did not plan for.
An Internal Job Record Exists Before Work Begins
Before a single hour is spent on a job, there should be a record in your system: job number, customer details, agreed scope, payment milestones, and who in your business is responsible for delivery. Without it, updates live in email threads and phone calls. When something goes wrong - and something usually does - there is nothing traceable to work back from.
A job record does not need to be elaborate. It needs to exist, to hold the confirmed scope, and to be the place where costs and progress are tracked throughout. Creating it before work starts, rather than partway through, means every hour and every cost is captured from the beginning rather than reconstructed later.
---
Confirming these four things before work begins takes a short conversation and a few minutes of administration. Scope accepted in writing, payment terms documented, suppliers briefed with firm dates, and a job record set up internally. The cost of skipping any one of them tends to show up at exactly the moment you are too busy with the job to deal with the ambiguity you left behind at the start.
Sources
- Construction Project Start-Up ChecklistSage Advice UK · accessed 2026-07-29
- The Ultimate Pre-Construction Checklist Every Contractor NeedsContractor Foreman · accessed 2026-07-29
- 7 Common Costing Mistakes UK Builders Must AvoidComet Estimating · accessed 2026-07-29
Related pages
Ready to run your business
on one platform?
Book a free demo and see how Zigaflow fits your team.