Lesson objective

Run an assisted contracting task through seven fixed steps, from assembling the controlling documents to a named owner's decision, so every output is interpreted, validated, challenged, authorised, assigned, documented and reviewed.

Plain-language explanation

Why this matters now

Triage decides whether a task may use AI and on what terms. This lesson is what happens next: the same seven steps, in the same order, every time, so two project engineers doing the same task produce work a project manager can check the same way.

The steps borrow their shape from the one construction source that names the gap.

The steps are fixed because construction errors are quiet on paper. A wrong dimension looks like a right one. A scope sentence that quietly drops an exclusion reads as smoothly as one that keeps it.

A question to sit with

A project engineer produces a scope summary for a mechanical subcontract in two minutes and spends fifteen checking it against the subcontract and Section 23 05 00. A colleague produces the same summary and forwards it. Three months later the subcontractor disputes a back-charge. Which of the two can show what happened?

What goes wrong

Starting with the question instead of the documents. "Summarise the electrical scope on this job" asks the model to supply facts it was never given.

Using the wrong version. The drawings were revised last week, the addendum changed the specification, and the paste came from the bid set.

Letting the draft become the source. After two rounds of edits nobody has looked back at the subcontract.

Checking the easy items only. Section numbers and dates get checked; the sentence that quietly turned "by others" into "included" does not.

Accepting instead of challenging. Validation asks whether the output matches the documents. Challenge asks what it left out, what it assumed and what a subcontractor would argue.

Nobody assigned to act. The summary is filed, but no one is told to send it, price it or build from it, so three people act on three versions.

The practical answer

Seven steps. They are this programme's recommendation, mapped to the governed decision translation framing.

Step What you do Governed translation Must be true before moving on
1. Name the output and owner One sentence: what will exist, who signs Authorised (in advance) A named person, not a role
2. Assemble the controlling documents Current drawing revision, specification section with addenda, executed contract or subcontract, adopted code text Interpreted (inputs) Every document identified by revision or date
3. Write the instruction Task, audience, format, constraints, refusal when documents are silent Interpreted "Use only the supplied documents" is in it
4. Generate the draft In the approved system — System approved for this data class
5. Validate and challenge Check every item against its document, then look for what is missing Validated, challenged Every checkable item checked, not sampled
6. Owner's decision and assignment The owner decides and says who acts on it Authorised, assigned Anything design, code or safety has gone to its owner
7. Record and review Log the task, documents, checks, corrections, owner; review later Documented, reviewed Written now, not reconstructed

Step 2: the documents are the point. Whatever the model did not receive, it may invent. Whatever it did receive, you can check against. Identify each document precisely: "Drawings E-101 to E-104, Revision C, issued 4 September; Section 26 05 19 as issued with Addendum 2; executed electrical subcontract dated 12 August." For a code question, supply the adopting jurisdiction's text with its amendments, because the International Code Council describes adoption as a law that incorporates the code by reference and may amend it.

Step 3: four constraints travel with every instruction.

  1. Use only the supplied documents; where they are silent, say "not stated" rather than filling the gap.
  2. Quote the sentence and give the sheet, section or page for every item.
  3. Make no design, code-compliance or safety determination; flag the question instead.
  4. Flag any conflict between documents without resolving it; the executed contract, the design professional and the project manager decide which governs.

Module 02 builds these into a full prompt architecture.

Step 5: validate, then challenge. Validation is a list.

Item Checked against
Scope inclusions and exclusions The executed subcontract and its exhibits
Section numbers and titles The project manual as issued, with addenda
Sheet numbers, details, dimensions The drawings at current revision
Dates, durations, notice periods The executed contract documents
Quantities and amounts Recomputed by the estimator, never taken from the draft
Code requirements Not settled by the preparer; routed to the adopted text and the building official

An AI output is never proof. A section number, a clause reference or a code requirement produced by a model is checked against the document before anyone relies on it.

Challenge is three questions: what did the documents say that the draft does not, what did the draft say that the documents do not, and what would the other party argue from this wording?

Step 6: authorise and assign. Workload is exactly when review weakens.

Bid day and month-end are the normal condition of a contracting office, so the owner's decision is a named step with a named person. The owner also says who acts on the output and which version they act on.

Remember this

  • Supply the controlling documents at their current revision; never ask the model to recall them.
  • Four constraints: supplied documents only, quote and locate every item, no design, code or safety determinations, flag conflicts without resolving them.
  • Validate every item, then challenge for what is missing or arguable.
  • The owner decides and assigns who acts, on which version.
  • Record it now; the record is the "documented, reviewed" end of governed translation.

Construction example

Kestrel Ridge Builders is a fictional general contractor building a two-storey medical office shell. The project engineer, Tomasz Wielgus, is asked for a scope summary of the fictional roofing subcontract for the superintendent. Step 1: the output is a one-page scope summary, owned by the project manager, Renata Colfax. Step 2: Tomasz supplies the executed roofing subcontract with its scope exhibit, Section 07 54 23 as issued with Addendum 1, and roof plan A-501 at Revision B. He notes that Revision C of A-501 was issued yesterday and swaps it in. Step 3: his instruction says to use only those three documents, quote and locate every item, make no design or code determination, and flag conflicts. Step 4: he runs it in the company's approved assistant. Step 5: validation finds that the draft lists "roof hatch curb flashing" as included, but the scope exhibit says it is by the sheet-metal subcontractor; the draft also gives the warranty as 20 years, while the section says 15. Challenge finds that the draft never mentions that Revision C added two drain locations. Tomasz corrects all three and flags the drains as a question for Renata. Step 6: Renata checks the inclusions, the warranty and the drains herself, decides the drains need a clarification from the roofing subcontractor, and assigns the superintendent, Eli Brandt, to walk the summary with the roofing foreman, using Revision C only. Step 7: Tomasz records the task, the three documents with revisions, the three corrections and Renata's decision. Checking took 18 of the 25 minutes.

Responsible-use warning

Do not let the draft replace the documents. After the first round of edits it is easy to work only from the text on screen, and from then on nothing is being checked. Validation means returning to the drawing at its current revision, the specification section with its addenda and the executed subcontract for every item, not sampling the easy ones. A fluent sentence that moves an item from "by others" to "included", or states a warranty period the section never gave, is how a wrong fact leaves a contractor under its own name.

Human-review requirement

The named owner decides before the output is used: the project manager for scope summaries, letters and owner communication; the estimator for anything priced; the qualifying individual for anything touching workmanship or construction operations. Design questions go to the architect or engineer of record, code compliance to the building official, and safety decisions to the person the company's safety programme names. The owner checks the validation list rather than repeating it blind, confirms the challenge questions were asked, names who will act and on which document revision, and confirms the record entry exists.

Practical exercise

Use a fictional company, project and documents only.

  1. Choose one recurring document task from your role and describe it in one sentence.
  2. Write step 1: the output and its named owner.
  3. List the step 2 controlling documents, each with a fictional revision letter, issue date or addendum number, and note how you confirmed each is current.
  4. Write the step 3 instruction with all four constraints in your own words.
  5. Write a fictional draft output yourself that contains one wrong inclusion, one wrong date or period, and one silent omission from a later revision.
  6. Build the step 5 validation list: every checkable item and its document.
  7. Write the three challenge questions and answer them for your draft.
  8. Write the owner's decision note, including who acts on it and which revision they use.
  9. Write the step 7 record entry.
  10. Write a note to the person you assigned, naming the exact revision they must use and what to do if a newer one is issued.
  11. Map each of your steps to the seven words of governed decision translation and note any you missed.
  12. Swap drafts with a colleague, repeat steps 6 and 7 on theirs, and list what each of you caught that the other did not. Record everything in your workbook.

Knowledge check

  1. What seven actions make up "governed decision translation", and where does the framing come from?

    Answer guidance: Interpreted, validated, challenged, authorised, assigned for implementation, documented and reviewed. It comes from the Vrcelj and Sandanayake preprint (July 2026), which is not peer reviewed.

  2. Name the four constraints that travel with every instruction in this workflow.

    Answer guidance: Use only the supplied documents and say "not stated" where they are silent; quote and locate every item; make no design, code or safety determination; flag conflicts between documents without resolving them.

  3. How does challenge differ from validation?

    Answer guidance: Validation checks each item against its document. Challenge asks what the documents say that the draft omits, what the draft says that the documents do not, and what the other party would argue.

  4. Why is assignment part of the owner's step?

    Answer guidance: An output nobody is told to act on, or that several people act on in different versions, fails in the field. The owner names who acts and on which document revision.

Sources and further reading