Why Submittal Logs Fail on UK Projects
On a £4.2m commercial fit-out in Manchester, a mechanical subcontractor submitted shop drawings for a bespoke air handling unit six weeks into the programme. The employer's agent took 28 days to respond — then rejected the drawings without clear reasons. The subcontractor resubmitted. Another 21 days passed. By the time approval came through, the long-lead procurement window had closed, delivery slipped by nine weeks, and the project overran by £180,000 in preliminaries. The submittal log? A shared spreadsheet nobody had updated since week three.
This scenario plays out constantly across UK construction. Submittal logs are treated as administrative housekeeping rather than contract management tools. Under JCT and NEC4, that distinction carries serious financial and legal consequences. As we covered in our guide to avoiding costly contract gaps, the documentation you maintain during delivery is often worth more than the contract itself when disputes arise.
What JCT and NEC4 Actually Require
Most site teams know submittals exist. Fewer understand how each standard form treats them — and those differences matter enormously when you're claiming an extension of time or defending a delay notice.
Under JCT Design and Build 2016, the Contractor's Design Submission Procedure (CDSP) governs how drawings, specifications, and calculations are submitted to the Employer's Agent. Clause 2.9 requires the contractor to submit documents in accordance with the agreed Information Release Schedule. If no schedule exists, the contractor must submit with "reasonable time" for review. That phrase is deliberately vague, and it becomes a battleground in adjudication.
Under NEC4 Engineering and Construction Contract, the process is more structured. Clause 27.1 requires the contractor to submit particulars for acceptance, and Clause 13.4 sets a two-week default response period unless the contract data specifies otherwise. Critically, if the project manager fails to respond within the stated period, the contractor can notify under Clause 13.8 — and a deemed acceptance may follow. This is a significant lever that many subcontractors never use.
Missed Response Deadlines = Missed Claims
Under NEC4, if you don't formally notify the project manager of a late response, you lose the right to claim any resulting delay as a compensation event. The eight-week notification window under Clause 61.3 is unforgiving. A poorly maintained submittal log means you can't prove when you submitted — or when the clock started.
Building a Submittal Log That Holds Up
A robust submittal log isn't a spreadsheet with columns for "submitted" and "approved." It's a timestamped audit trail that maps directly to your contract's review obligations, your programme's critical path, and your payment application narrative.
Every entry should capture: submittal reference number, revision status, date transmitted, contractual review period, required response date, actual response date, outcome (approved, approved with comments, rejected), resubmission date if applicable, and the impact on procurement or installation if delayed. Critically, transmittals must be issued formally — email with read receipt at minimum, RFI or formal notice under the contract where required.
Linking Submittals to the Programme
Each submittal should be tied to a specific activity on the construction programme. If the approval of a structural steel connection detail is on the critical path, and the employer's agent takes 35 days instead of the contracted 14, that delay is a compensation event under NEC4 Clause 60.1(6) — but only if you can demonstrate the linkage. Your submittal log should make that linkage explicit, referencing the programme activity ID alongside the submittal entry.
Building Safety Act 2022 Implications
For higher-risk buildings — those over 18 metres or seven storeys — the Building Safety Act 2022 introduces additional gateway requirements that directly affect submittal sequencing. Gateway 2 requires full building control approval before construction begins, and Gateway 3 requires sign-off before occupation. Fire and structural submittals for in-scope buildings must be tracked separately, with a clear record of who approved what and when. A standard submittal log won't capture this without modification.
Flag Contract Risk Before It Costs You a Claim
Trueleveler's Contract Review engine analyses JCT and NEC4 subcontracts for clause-level risk, highlighting vague review periods, one-sided rejection rights, and missing submittal procedures before you sign.
Clause Language That Creates Exposure
Review the submittal provisions in your subcontract carefully. Employers and main contractors routinely insert bespoke amendments that shift risk onto the subcontractor — often without making them obvious.
This clause, drawn from an actual bespoke amendment to a JCT DB 2016 subcontract on a £9m logistics warehouse in the East Midlands, effectively strips the subcontractor of any entitlement for employer-caused review delays. It's enforceable. The Housing Grants, Construction and Regeneration Act 1996 protects payment rights and adjudication access, but it doesn't override freely negotiated time-risk allocations. As detailed in our post on contract clauses every GC should red-line, amendments like this require pushback at tender stage — not after mobilisation.
Best Practice: Agree the Submittal Schedule at Award
Before signing, negotiate and attach a Submittal Schedule as a contract document. Define each submittal type, the review period, the required response format, and the consequences of late response. Under NEC4, this can be incorporated into the Works Information. Under JCT, it becomes part of the Contract Documents. Once embedded, it's enforceable — and it removes the "reasonable time" ambiguity that costs contractors dearly in adjudication.
Using Adjudication Rights to Protect Your Position
The Housing Grants, Construction and Regeneration Act 1996 gives every party to a qualifying construction contract the right to refer a dispute to adjudication at any time. Submittal-related delays — particularly where they've caused procurement disruption, prelims overrun, or loss of productivity — are among the most common grounds for adjudication on UK projects. But adjudicators require evidence. A well-maintained submittal log, cross-referenced with formal transmittals, programme updates, and payment application narratives, is often the difference between a winning and losing referral.
For further context on how contract documentation supports risk management at every project stage, see our overview of AI in construction contract risk management.
The Bottom Line
Submittal logs are not administrative overhead — they are live contract management instruments. Under JCT, they substantiate your entitlement to time and money when the employer's review process overruns. Under NEC4, they trigger the compensation event mechanism and support deemed acceptance claims. Under the Building Safety Act 2022, they form part of the mandatory golden thread of information for higher-risk buildings. A log that slips is a claim that disappears.
The fix isn't complicated, but it requires discipline from week one: formal transmittals, timestamped entries, programme linkage, and contractual review periods tracked against actuals. Pair that with a thorough review of your subcontract's submittal clauses before you sign — particularly any bespoke amendments that limit your entitlement for review delays — and you'll be in a materially stronger position when disputes arise. In UK construction, the projects that avoid costly adjudications aren't the ones with fewer problems. They're the ones with better records.