Lesson objective
Scale an AI governance programme to the size and risk of a contracting company, keeping the same essential elements whether it runs to one page or a full charter.
Plain-language explanation
Why this matters now
A two-person remodeller and a four-hundred-person commercial builder face the same underlying questions: which tools, for what, with whose data, reviewed by whom, and what happens when something goes wrong. They should not write the same document. A charter with committees and quarterly reviews would sink a two-person company. A one-page note would leave a large builder with thirty project teams making up their own rules.
The voluntary sources support scaling rather than a fixed form. ISO describes ISO/IEC 42001 as for "organizations of any size involved in developing, providing, or using AI-based products or services". AIA's AI Firm Toolkit, written for architecture firms, is described as a resource for firms "of any size". ABC's 2025 guide recommends a formal policy that defines its purpose and the technologies covered, and designating point people. None of these binds a contractor, and none prescribes a length.
What should not scale away is the core: a named owner for each output and a record that the review happened. AI Coalition Network's educational standard is that a named, qualified professional reviews and owns every AI-assisted deliverable before it reaches a client, a regulator or a filing, and that the review is recorded. That standard is the same for both companies. It is a teaching standard of this programme, not a legal requirement.
A question to sit with
If your company doubled in size next year, which parts of your AI programme would still work, and which depend on everyone knowing everyone?
What goes wrong
The small company copies a large company's template. A remodeller downloads a thirty-page policy, fills in the blanks and files it. It names committees that do not exist. Nobody reads it, so the real practice is whatever the owner does on the day.
The small company writes nothing. "It is just the two of us, we know what we do." Then a homeowner asks what happens to the photographs of their house, or a subcontractor asks whether the company used AI on its scope, and there is no answer on paper.
The large company scales the paperwork but not the ownership. A charter, a committee and a policy library exist. Project teams still do not know who approves a tool on their job, and thirty sets of local practice grow underneath.
Growth outruns the programme. A twelve-person company with a one-page note wins a large project, hires fifteen people and opens a second office. The note still says "Dana reviews everything," and Dana cannot.
The practical answer
Choose the form by size and risk. The table is an AI Coalition Network recommendation.
| Company | Form | Owner | Review |
|---|---|---|---|
| Owner-operator or two to five people | One-page AI note | The owner | Owner reviews every outside-facing AI output; look again every six months and when a tool changes |
| Six to about fifty people | Short programme: purpose, inventory, decision rights, minimum review by tier | A named accountable leader, often the owner or operations lead | Inside the regular operations meeting; scheduled review twice a year |
| About fifty to several hundred | Full programme as in Lessons 1 to 3, point people by department or region | Accountable leader with a deputy, reporting to ownership | Inside quality and management review cycles; triggers as in Lesson 3 |
| Several hundred and up, several offices or states | Charter approved by ownership or board, programme, inventory, point people per office | Accountable executive, with regional deputies | Formal management review; periodic independent check, which Module 12 covers |
What the two-person remodeller writes. A one-page note, signed and dated by the owner, with six short sections:
- Tools we use, and what each is for.
- What we never do with them, such as put a homeowner's personal information into a tool not set up for it, send a drawing change without the designer, or let a tool write a contract notice.
- Who checks: the owner reads every AI draft that goes to a homeowner, a subcontractor, an inspector or a supplier, against the plans, the specifications and the contract.
- What we keep: the reviewed version of anything sent, in the job folder.
- When we stop: if a tool gets something wrong that reached a customer, we stop using it for that job until we understand why.
- When we look again: every six months, and whenever we add or change a tool.
That note meets the same core standard as a charter. It is also short enough that the owner will read it again.
What the four-hundred-person builder writes. A charter and a programme:
- Charter, approved by ownership: purpose, scope, the accountable executive and their authority including stop authority, reporting to ownership, and how the charter changes.
- Programme: the inventory, the data bands, the decision-rights table, minimum review by consequence tier, the point-person network, records, the review cycle and triggers, and how each element sits inside existing quality, safety, IT and management review processes.
- Office and project layer: a one-page summary for each project team, so a superintendent on a new job can find the rules in five minutes.
- Links out to the security programme, supplier assessment, contract terms and workforce rules, covered in later modules.
Keep the thread between the two. Whatever the size, the programme should state plainly that it is the company's own choice, drawing on voluntary guidance, and that no contractor licensing board has published AI guidance. It should also say that the duties it serves are fixed by law and do not shrink with company size: the licence, supervision of construction operations, the design professional's responsibility for design, the employer's safety duties and each signer's signature.
Plan for growth. Add a line to the small company's note: "When we have more than [number] people or a second office, we move to the short programme." Set the number in advance. Growth is the moment a programme most often fails, because everyone is busy and the old way still seems to work.
Remember this
- The six questions are the same at every size: which tools, for what, with which data, who owns and reviews, who can stop, when do we look again.
- A two-person remodeller writes a signed one-page note; a large builder writes a charter, a programme and a project-level summary.
- Scale the paperwork, never the core: a named owner reviews each output and the review is recorded.
- Voluntary sources describe themselves as usable by organisations of any size; none prescribes a length and none binds a contractor.
- Write the growth trigger in advance, because growth is when programmes fail.
Construction example
Two fictional companies write their programmes in the same month. Maria and Joe Castellano run Castellano Home Renovation, a two-person remodeller. Maria uses a drafting assistant for estimates and homeowner emails, and Joe uses a phone app that measures rooms from photographs. Their one-page note lists the two tools; says they never put homeowners' personal details into the drafting assistant, never send a drawing change without the homeowner's designer, and never let a tool write the contract's required notices; says Maria reads every draft against the plans and the contract before it goes out; keeps the sent version in the job folder; stops a tool for the job if it gets something wrong that a homeowner saw; and sets a review every January and July. They add: "When we have more than five people, we move to a short programme." They sign and date it. Across town, Harrow Creek Construction, a fictional 400-person commercial builder with offices in two states, writes a charter approved by its board. The charter names the chief operating officer, Dana Whitcombe, as accountable executive, with stop authority and a quarterly report to the board. The programme includes an inventory of 23 rows, four data bands, a decision-rights table, four review tiers and a point person in each of four regional offices. Each of the 31 active projects receives a one-page summary. Because the company works in two states, the charter says the programme does not state any licensing rule and each regional office checks its own state and local requirements. In January, both companies find a tool that changed without warning. Maria spots it in her six-monthly look. Harrow Creek catches it through a vendor-change trigger. Both fix it the same way: they pause, check, and update the row.
Responsible-use warning
Do not copy a large company's AI policy template into a small company and file it. A document that names committees and reviews that do not exist is worse than none: it states practices the company does not follow, and someone may one day ask for the evidence. Equally, do not let a large company confuse a long policy library with ownership. The test at every size is whether each output has a named owner and a recorded review.
Human-review requirement
At every size, the owner or principal approves and signs the programme. In a two-person company the owner is usually also the output owner for everything that leaves the company, and checks each AI draft against the plans, specifications and contract. In a large company the accountable executive holds the programme and reports to ownership or the board, while project managers, the qualifying individual, competent persons and signers own their outputs. Whoever approves checks that the form fits the company and that the core standard has not been scaled away.
Practical exercise
Use a fictional company for each part.
- Write the one-page note for a fictional two-person remodeller, using the six sections in the lesson. Keep it to one page.
- Sign and date it as the owner, and add the growth trigger with a specific number of people.
- For a fictional 400-person builder, draft the charter's five elements in one or two sentences each.
- List the sections of that builder's programme and where each lives in its existing processes.
- Draft the one-page project summary a new superintendent would read on day one.
- Take one rule, such as review of AI drafts sent to owners, and write it at both sizes.
- For a fictional 45-person company that has just won a large project, list which parts of its current note will fail first as it grows.
- Write the sentence both programmes must contain saying the programme is the company's own choice, drawing on voluntary guidance, and that no licensing board has published AI guidance.
- Compare your two documents side by side. For each of the six core questions, confirm both give an answer, and mark where the large builder's answer adds structure rather than substance.
- Decide which size band your own company, or a fictional one you know well, falls into today and which it will fall into in two years. Note the first change you would make now.
Knowledge check
-
What six questions must an AI programme answer at every company size?
Answer guidance: Which tools, for what work, with which data, who owns and reviews the output, who can stop a use, and when the company looks again.
-
What does a two-person remodeller write instead of a charter?
Answer guidance: A signed one-page note listing the tools, what they are never used for, who checks each draft against the plans and contract, what is kept, when use stops, and when the note is reviewed.
-
Which part of the programme must never scale away as a company shrinks or grows?
Answer guidance: The core standard: a named owner reviews each AI-assisted output before it leaves the company and the review is recorded. The legal duties it serves do not shrink with company size.
-
Why write a growth trigger into a small company's note?
Answer guidance: Because growth is when programmes most often fail: everyone is busy and the old way still seems to work. Setting the trigger in advance forces the move to a fuller programme.
Sources and further reading
- AI Coalition Network — Certification Educational Standard: Human Review of AI-Assisted Professional Work. Accessed 2026-09-15.
- International Organization for Standardization (ISO) and International Electrotechnical Commission (IEC), ISO/IEC JTC 1/SC 42 — ISO/IEC 42001:2023 Information technology — Artificial intelligence — Management system (2023-12-18). Accessed 2026-09-15.
- American Institute of Architects (AIA) — AIA AI Firm Toolkit (2026-08-28). Accessed 2026-09-15.
- Associated Builders and Contractors (ABC), guide produced by GCM — 2025 AI Resource Guide for Construction Professionals. Accessed 2026-09-15.