Level 4 taught a contracting company to govern AI. Level 5 is about building the part that acts. A drafting assistant suggests; an automation does. It logs an enquiry, assembles a bid package, posts to the project management system, sends a transmittal, updates a cost code, and when it is wrong the error has already reached the owner, the subcontractor or the ledger by the time anyone looks. This level teaches automation whose authority is bounded in writing, whose every action is recorded, and whose failures are caught by design rather than by luck.
The first three modules set authority and orchestrate the two flows where automation pays off and fails most expensively. Module one climbs the ladder from suggesting to acting, names the three root causes of runaway automation, builds the automation authority register, and lists what never goes to an automation: seals, signatures, notices, waivers, money and advertising. Module two orchestrates enquiry intake, qualification, bid assembly and award while a qualified person decides price, scope and subcontractor selection, and treats consent, do-not-call and revocation rules for automated calls, texts and AI voice as hard requirements. Module three treats a deadline automation as a reminder and never the last line of defence, sources every notice, lien and contract date from the statute or the executed document, with California as the worked example, and sets what may be automated around trust funds, bonds and prompt payment.
Modules four to six are the integrations. Module four maps every system an automation reads from and writes to, writes a data contract for each boundary, makes classification codes and the execution plan rules an integration obeys, and settles whether an owner's or designer's digital data may move at all. Module five connects to project management and document control read-only first, earns each write with evidence, keeps proposed documents out of the contract record, and stops a retry from sending the same transmittal three times. Module six works near money and certifications: an automation may assemble, reconcile and flag certified payroll, payment applications and lien waivers, and never signs, certifies, releases or pays, with separation of duties that holds in an office of three.
Modules seven to nine are human control. Module seven designs approval gates for a superintendent with four minutes and a phone, decides what the approver must see, explains why automation bias makes a gate decay with repetition, and samples what passed through. Module eight gives every automation its own identity, credentials and named owner, scopes access across office, trailer and field, keeps owners, projects and joint ventures apart, and offboards an automation when a project closes. Module nine covers who may stop an automation and how, work in flight, the manual route and the deadlines that keep running, a site with no signal, and the careful return to automation.
Modules ten to twelve are defence and observation. Module ten threat-models submittals, scanned drawings, invoices and inbound mail as carriers of instructions, from the defender's side only, and bounds tool permissions so a fooled automation cannot do anything important. Module eleven specifies the action record, what never to log, retention aligned to duties that already apply, and a tamper-evident trail an owner's auditor, an insurer or a lawyer can follow. Module twelve finds failures that raise no error, sees systematic errors across projects and divisions, sizes alerts to consequence, caps cost, and re-baselines after every model or vendor change.
Module thirteen responds when an automation has already sent fourteen notices or a wrong figure to an owner: containment, rollback and correction, who is told in what order, and the evidence for the review that decides what runs again. Module fourteen measures against a baseline taken before the change, counts review time, refuses double-counted savings, and takes an automation from one pilot job to standard practice with stop criteria written in advance. The capstone is the Automation Implementation Project for a fictional contractor. The level ships with a printable workbook and nine templates, and the examination draws forty scenario questions from a reviewed bank.
Everything here is professional education. It is not engineering, design, legal, insurance, security or safety advice; it does not replace a licensed design professional's seal, the authority having jurisdiction, a competent person on site, legal counsel, or the executed contract and the law of the state where the work is performed. Completing the level earns an independent educational certificate issued by AI Coalition Network with a public verification page. It is not a contractor licence, a trade, safety or security credential or a compliance certification, it carries no professional education hours, and it satisfies no licensing, registration or safety-training requirement.