Coordination becomes harder when several crews, suppliers and specialists are involved. One agreement stays in WhatsApp, another in a phone call, photographs are saved without references, and a payment request uses a different description from the estimate.
The solution is to turn each agreement into a verifiable cycle: scope, plan, evidence, acceptance and payment. The contractor knows what to deliver, while construction management knows what to check before authorising resources.
Contents:
A common system for all contractors
Control depends on everyone using the same references: work items, quantities, dates, responsible people and acceptance criteria. Sending more messages alone does not provide this.
When these details are stored in different places, management spends time reconstructing events. The contractor and the client may also interpret progress differently.
A simple system connects five elements. Scope defines what will be done; the programme states when; evidence shows how much was completed; acceptance confirms compliance; payment closes the cycle.
| Element | What must be clear | Minimum evidence |
|---|---|---|
| Scope | Items, quantities, exclusions and specifications | Estimate or scope attachment |
| Programme | Dates, sequence and deliverables | Schedule or weekly plan |
| Progress | Completed quantity and location | Measurement, report and photographs |
| Acceptance | Quality criterion and outstanding observations | Approval by the responsible person |
| Payment | Authorised amount, deductions and balance | Approved payment statement and payment evidence |
Select for capability and define scope before starting
Price alone is insufficient for selection. Review experience with comparable work, staffing and equipment capacity, references, actual availability and how progress is reported. A cheap offer loses value if it requires constant supervision or causes rework.
Before starting, walk through the work area with the contractor. Confirm existing conditions, access, storage, supplies, obstructions and other teams’ work. Initial photographs help distinguish pre-existing damage from execution problems.
The scope must state inclusions and exclusions, with measurable units and quantities. Phrases such as “complete installation” or “finished surface” leave room for interpretation unless they cover materials, preparation, testing and cleaning.
Define who supplies materials, who receives them, who is responsible for waste and how substitutions are authorised. These decisions affect cost, time and warranty.
Document agreements affecting cost, time and quality
The contract and its attachments should function as working instructions. They need to identify the subject, scope, price or calculation method, programme, acceptance, warranties, responsibilities and change procedure.
The estimate connects scope with money. Its work items must correspond to how progress will be measured. For an item-based engagement, the payment statement must use those same items; for deliverables-based work, each deliverable needs a verifiable criterion.
Additional work requires prior approval whenever possible. The request should describe the reason, quantity, cost and programme impact. A verbal instruction can resolve an immediate problem and cause a dispute at completion.
Keep a decision log. It can be brief: date, issue, decision, responsible person and related evidence. It should remain accessible later without relying on someone’s memory.
Agree on the change procedure
- The contractor identifies a new condition or request.
- The contractor presents the scope, cost and effect on time.
- Management reviews the proposal and its dependencies.
- The authorised person approves, rejects or adjusts it.
- The change is incorporated into the current estimate and programme.
This procedure prevents teams from executing first and negotiating later. It also protects the contractor when the change was requested and documented.
Control construction with a weekly cycle
Frequent reviews reduce uncertainty. Agree on a weekly cut-off to review the plan, progress, constraints, quality and estimated amount rather than waiting for month-end.
The contractor prepares a short report with completed work, quantities, photographs, relevant materials, outstanding items and decisions needed. The person responsible for the site checks the work area before accepting progress.
The weekly meeting should look backwards and forwards. First validate what was done; then confirm the next work, required materials and potential obstructions to the following period.
- The weekly plan by work area and responsible person.
- Progress measured against items or deliverables.
- Quality observations with correction deadlines.
- Critical purchases and supplies.
- Changes awaiting authorisation.
- The amount potentially payable after acceptance.
A report without decisions merely moves the problem into another format. Every constraint needs an owner and a date: release a drawing, confirm a measurement, receive materials or correct a defect.
Connect progress, payment statements and payments
Payments should follow accepted progress. Cash urgency is insufficient grounds for payment. The contractor submits quantities or deliverables; supervision checks them; differences are clarified; the corresponding amount is then authorised.
Advances require different rules. Define their purpose, recovery method, evidence of use and outstanding balance. Mixing advances with progress payments obscures what has actually been completed.
The payment statement should show the period, items, contracted quantity, previous quantity, current-period quantity, cumulative total and quantity remaining. Show retentions, deductions and advance recovery separately where applicable.
Tax documentation and payment evidence support the administrative process but do not replace technical validation. An invoice documents a transaction; it does not by itself establish acceptance of quantity and quality.
Check quality before work is concealed
The most costly faults are often discovered after an installation has been covered or another contractor has built over it. Inspection points should therefore be defined before work starts.
For concealed work, agree on photographs, location, required testing and the person responsible for releasing the next step. Link the file to the relevant item or work area so it remains identifiable beyond a general photo album.
Observations need a status. Record what was found, who will correct it, the committed date and closure evidence. A photograph of a defect without follow-up does not provide control.
Prepare a partial handover at the end of each stage. Reviewing by stages reduces outstanding issues at the end and helps resolve responsibilities while the team is still on site.
How to organise contractor management in 101
101 brings projects, participants, estimates, documents, reports and event history into one environment. It becomes useful when contractors report against the agreed structure and management reviews the same information.
Maintain a common catalogue of work and use it in estimates and reports. An item can then retain the same name from contracting through progress verification.
Documents and photographs should accompany the event they support. This connection makes it easier to review a payment, explain a change to the client and reconstruct project history without chasing scattered messages.
The official 101 page presents the platform’s general capabilities. Before adding contractors, define permissions, people responsible for validation and a review frequency the team can sustain.
Technology does not replace the contract, supervision or professional responsibility. Its role is to preserve the connection between work, time, evidence, acceptance and money.
When that connection is maintained throughout construction, payments become the consequence of verifiable progress and stop being isolated disputes.
