AI for UK Civil Engineers and Testers: NEC4, CDM, Prompts
AI drafts of NEC4 notices, site diaries, RAMS and test cases in the UK, with Eurocode checks, CDM duties and sign-off kept by the engineer. With masking examples.
By Redbison Dev · · 9 min read

United Kingdom edition. Written for UK practice: NEC4 and JCT terms, CDM 2015 duty holders, Eurocodes with UK National Annexes, WCAG 2.2 for public sector sites and UK test data formats such as NI numbers. US edition
On a UK project the paperwork has its own vocabulary. A civil engineer drafts early warnings and compensation event quotations under NEC4, method statements for a RAMS pack, and site diaries that may end up as evidence in a dispute. A software tester writes test cases against user stories, bug reports, and accessibility checks against WCAG 2.2 for a public sector service. In both jobs a general AI assistant can do the first draft of the wording well. In both, the part it gets wrong is the part that matters: the contract clause, the Eurocode reference, the expected result nobody specified. This guide covers where AI drafting fits UK engineering and testing work, the contract and data issues, worked examples from the AI Prompts for Civil Engineers (UK) and AI Prompts for Software Testers (UK) kits, and a review routine.
Drafting versus engineering judgement on UK work
| Good fit for an AI draft | Stays with the engineer or tester |
|---|---|
| Wording of an NEC4 early warning from your facts | Whether the matter is a compensation event, and the notification timing |
| Minutes of an early warning meeting with an action table | Agreeing the risk reduction measures |
| Method statement skeleton for a RAMS pack | Temporary works design and the temporary works procedure |
| Daily site diary from rough notes | What counts as a defect or an instruction |
| RFI response wording from your technical answer | The technical answer |
| Test cases with boundary values from a user story | What the story actually requires |
| Bug report from reproduction notes | Severity and priority |
| WCAG 2.2 test charter for a public sector form | The audit result and the accessibility statement |
On NEC4 contracts the language is precise. The Engineering and Construction Contract asks the parties to act in a spirit of mutual trust and co-operation and to give early warnings of anything that could affect time, cost or quality, and it handles change through compensation events. A model trained mostly on American material will happily write "change order" and "owner", or mix NEC4 terms with JCT ones. The UK setting in the kit tells it to use the contract's own terms (early warnings, compensation events and the Project Manager under NEC4; variations, relevant events and the Contract Administrator under JCT) and never to mix forms.
The standards a model gets wrong
Eurocodes. BSI notes that Eurocodes have been the primary standards for structural and geotechnical design in the UK since 2010, used with UK National Annexes. The suite is changing: BSI lists BS EN 1990-1:2023+A1:2026, BS EN 1990-2:2026 and the UK National Annex to BS EN 1990-1:2026 as published parts of the next generation. That is exactly the kind of edition detail a model will get wrong from memory, so the kit asks it to name a code only as given in your material or to write [VERIFY CLAUSE]. A model can list the checks you should recompute in a calculation; it cannot verify a design to the edition named in your contract.
CDM 2015. The Construction (Design and Management) Regulations 2015 set out the duty holders (commercial and domestic clients, designers, principal designers, principal contractors and contractors), and HSE explains how to notify a project on form F10. The kit tells the model to use those duty-holder names and never to state that a document is compliant: whether a construction phase plan or a RAMS meets CDM is a judgement for the people who hold the duties.
Accessibility. GOV.UK guidance says the public sector accessibility regulations came into force on 23 September 2018 and that public sector websites and apps must meet WCAG 2.2 AA (unless there is a valid legal reason not to) and publish an accessibility statement. For a public sector product, the UK testers' kit sets WCAG 2.2 AA as the target in accessibility test charters; for other products it uses the level the team has agreed.
Masking site diaries and bug reports
UK project documents are usually covered by confidentiality terms in the appointment or contract, and anything about people (a worker's name next to a near miss, a user's email in a log) is personal data under UK data protection law. The kits' masking helper runs in your browser. A made-up site diary entry:
Site diary 05/11/2026: Mr Dan Hughes (Bloggs Groundworks) reported a near miss at gridline C4; call him on 07700 900789. Email dan@example.com.
becomes:
Site diary [DATE-1]: Mr [NAME-1] (Bloggs Groundworks) reported a near miss at gridline C4; call him on [PHONE-1]. Email [EMAIL-1].
The subcontractor's name stays, because the helper has no way to know which company names are sensitive; remove it if the contract says so. A made-up bug report:
Bug: checkout fails for user jane.smith@example.co.uk, NI number QQ 12 34 56 A, postcode SW1A 1AA, IP 192.0.2.44.
becomes:
Bug: checkout fails for user [EMAIL-1], NI number [NATIONAL-ID-1], postcode [POSTCODE-1], IP [IP-1].
The NI number in the example is HMRC's own illustration of the format: two letters, six numbers and a final letter that is always A, B, C or D. That format matters for testers too. Test data should never contain a real NI number or NHS number, and HMRC's manual notes that some prefixes have been used only for administrative reference numbers, so a validator that accepts every two-letter prefix is wrong.
Worked prompts in the UK kit
An early warning notice built with the region set to United Kingdom carries constraints like these:
- Write for UK practice: British spelling, SI units, dates as 6 November 2026.
- Design references are normally Eurocodes published by BSI with the UK National Annex (for example BS EN 1992-1-1 for concrete) and the British Standards named in the contract. Name them only as given or mark [VERIFY CLAUSE].
- Use the contract's own terms and do not mix forms: under NEC4, early warnings, compensation events and the Project Manager; under JCT, variations, relevant events and the Contract Administrator.
- Use Construction (Design and Management) Regulations 2015 duty-holder names (client, principal designer, principal contractor) and never state that a document is compliant.
A test case prompt for a UK checkout story would add your story text and ask for boundary values on the postcode field (valid outward and inward codes, a lower-case entry, a missing space) with anything the story does not specify marked [QUESTION FOR PO]. The point is the same as in civil work: the model generates variations quickly, and you decide what the system is meant to do.
Review routine
- Trace every reference. Drawing numbers, clause numbers, programme dates and test IDs must come from your input.
- Recompute every number with a calculator, for example the Concrete Calculator (UK) for a pour quantity.
- Check every code citation in the edition your contract names; next-generation Eurocode parts are being published now.
- Check contract language against the form in use: one "change order" in an NEC4 notice is a sign the model drifted.
- Run generated test code and check it fails and passes for the right reasons.
- Sign or send only what you would have written. Anything issued under your name is yours under your institution's code of conduct, whoever drafted it.
A four-week trial
| Week | Civil engineers | Testers |
|---|---|---|
| 1 | Check your firm's AI policy and the confidentiality terms in the appointment. | Check whether code, logs and screenshots may be pasted, and into which tool. |
| 2 | Use the minutes and site diary templates on non-confidential notes. | Use the bug report and exploratory charter templates on internal issues. |
| 3 | Add early warnings and RFI responses, every clause checked against the contract. | Add test cases from stories and a WCAG 2.2 charter for one form. |
| 4 | Compare drafting plus checking time with your usual time; keep what wins. | Count defects found by AI-drafted cases and questions raised for the product owner. |
Frequently asked questions
Can AI check a Eurocode calculation?
It can list the assumptions, units and order-of-magnitude checks for you to recompute, but it cannot verify a design. It does not know your loads, ground conditions or the edition and National Annex your contract names, and new Eurocode parts are being published, so treat any clause it cites as unverified.
Can AI write an NEC4 early warning?
It can draft the wording from facts you give it: what the matter is, its possible effect on time, cost or quality, and what you propose. Whether to notify, and whether a matter is a compensation event, are contractual judgements for the people named in the contract.
What WCAG level do UK public sector sites need?
GOV.UK guidance says public sector websites and mobile apps must meet WCAG 2.2 AA, unless there is a valid legal reason not to, and publish an accessibility statement. The regulations came into force on 23 September 2018.
What does a UK National Insurance number look like?
HMRC describes it as two letters, six numbers and a final letter that is always A, B, C or D, for example QQ 12 34 56 A. Use clearly fictitious values like that in test data, never a real one.
Is it safe to paste a site diary into ChatGPT?
Only into a tool your company approves, and only after removing names, phone numbers and anything the contract treats as confidential. The masking helper catches names after a title, phone numbers, emails and dates, but not company names or project code names.
Sources and further reading
- The Construction (Design and Management) Regulations 2015, Health and Safety Executive. Duty holders and F10 notification.
- Eurocodes and UK National Annexes, BSI.
- NEC4 Engineering and Construction Contract, NEC. Early warnings and compensation events.
- Understanding accessibility requirements for public sector bodies, GOV.UK.
- NIM39110: what a NINO looks like, HMRC National Insurance Manual.
- Artificial Intelligence Risk Management Framework: Generative AI Profile (NIST AI 600-1), National Institute of Standards and Technology. Confabulation and other generative AI risks.
Open the AI Prompts for Civil Engineers
More AI for Professions
Every tool in the AI for Professions section, free and in your browser.