Teach The AI One Proven Workflow Before Writing The Playbook.

A building company can spend weeks writing an AI playbook for a process nobody performs the same way twice. The document looks complete. The agent follows it faithfully. Then the first live job reveals the missing judgment: which drawing controls, when a price needs reconfirmation, who can approve an alternate, or what makes an ordinary variance worth escalating. The problem began before the prompt. The team documented an imagined process instead of observing proven work.

OpenAI's September 1 workflow case study describes Basis demonstrating an onboarding process once, then packaging it as a reusable skill with a clear trigger, known steps, access to the right tools, and a definition of done. The Datum interpretation for remodelers, builders, designers, showrooms, suppliers, distributors, and trades is simple: before writing a large AI instruction set, have a trusted operator run one representative job packet while explaining the decisions that change the path.

Choose A Workflow That Already Has A Winner

Do not start with the workflow everyone agrees is broken but nobody owns. Choose repeatable work that one person can already complete well: preparing a selection-status update, checking a vendor quote against an estimate, assembling a permit submission packet, reviewing a change-order request, or producing a weekly project brief. The operator should be able to show both a normal case and a case that required judgment.

Procore defines a construction workflow as ordered tasks with responsibility assigned across collaborators. Its current guidance also warns that construction SOPs must leave room for geography, owner requirements, and project conditions. That tension is exactly what the demonstration should expose: which parts are company standard, which are project configuration, and which require a named person's decision.

Record The Decision Trail, Not Just The Clicks

Screen recordings and click lists capture mechanics. They rarely capture why the operator paused, rejected an apparently valid record, checked a second source, or called someone instead of continuing. During the demonstration, require the operator to narrate each decision point and identify the evidence that would let another qualified person reach the same conclusion.

• Trigger: the event that starts the work and the conditions that must already be true.
• Inputs: the approved documents, records, templates, and project settings required to proceed.
• Source order: which record controls when drawings, specifications, estimates, selections, messages, or schedules disagree.
• Decision points: the tests that determine the next step, including the evidence used for each branch.
• Permissions: what the AI may read, draft, compare, update, send, or never do without approval.
• Definition of done: the artifact, review, distribution, and record update that prove the workflow closed.
• Exceptions: the conditions that stop the standard path and the person who owns the next decision.

Build The First Playbook From Evidence

Turn the demonstrated run into a compact playbook. Keep instructions close to the templates, examples, source definitions, and output format they depend on. OpenAI Academy describes skills as reusable workflows supported by instructions and resources such as templates, examples, schemas, and tool access. For a building business, those resources should be approved company artifacts—not invented sample language that quietly becomes policy.

Separate facts the AI can extract from decisions the business must own. The system may read the stated allowance from a contract or compare two quoted model numbers. It should not decide that a substitution is acceptable, that a scope gap belongs to a trade partner, or that a client commitment can be made unless the playbook contains an authorized rule and the required evidence.

Test Against A Different Job

A playbook that reproduces the demonstration may only have memorized one project. Test it on a second job with a different owner preference, contract condition, vendor format, project phase, or exception. Ask the original operator to review the output and label every correction: missing source, wrong source order, ambiguous instruction, project-specific setting, permission violation, or genuinely new exception.

Do not patch each failure with another paragraph of prose. Improve the appropriate control. A missing field belongs in the input checklist. A recurring project difference belongs in configuration. A dangerous action belongs behind a permission gate. An uncertain judgment belongs in an exception queue. A measurable output error belongs in the test packet.

Let Exceptions Improve The Operating System

OpenAI's case study treats recurring onboarding questions and exceptions as signals for improving the skill before the next cohort. Use the same loop after launch. Preserve the agent's input sources, proposed work, reviewer corrections, final accepted artifact, and reason for escalation. Review repeated exceptions with the people closest to the work.

• Acceptance rate: how often the first draft is usable without material correction.
• Correction pattern: which fields, sources, or decisions people repeatedly change.
• Exception quality: whether the system stops for the right uncertain or consequential cases.
• Cycle time: elapsed time from a valid trigger to an accepted, distributed result.
• Rework avoided: downstream errors or duplicate effort prevented by the playbook.
• Coverage: which project types and conditions have been tested, and which remain unapproved.

Publish The Parts Customers Need

The internal playbook may contain private systems and decision rights, but parts of the workflow can become valuable public content: what information a client must provide, how selections are approved, what makes a quote complete, when lead times are reconfirmed, or how a change request moves from question to signed decision. Those pages demonstrate operating knowledge that a generic AI summary cannot replace.

Google says AI Overviews and AI Mode need no special AI-only schema. The durable search strategy remains helpful, original, crawlable content with structured data that matches what visitors can see. Publish real decision paths, keep source claims visible, and give the reader a useful next action.

The Datum Rule

Do not ask AI to formalize a workflow your team has not demonstrated. Start with one trusted operator, one representative job packet, one visible decision trail, and one accepted definition of done. Then test the playbook on a different project, route exceptions to accountable people, and let correction evidence improve the next version.

Turn Proven Work Into A Repeatable System

• An AI Workflow Is Not Real Until Someone Else Can Run It
• Your AI Workflow Needs a Shared Vocabulary
• Explore practical AI paths for your team

Next step, if this note maps to a problem on your desk: Book Private Training.