Limited published evidence · Construction and field services
AI change-order drafting for contractors: Ken Reiners recipe
A practitioner recipe asks AI to clarify job details and draft a one-page change order with work, price and date. The post says to send it before the crew starts; it does not establish who signs or report an executed case.
Draft a contractor change order before extra work begins
Contractor change-order drafting recipe (business unnamed)
Practitioner recipe published on X. No named contractor deployment, executed draft, signature, customer acceptance or operating result is established.
A published third-party example, not a Nuvepro customer case or evidence of a partnership.
The workflow at a glance
Draft a change order before extra work begins
Illustrative summary of the published account
- Human input in recipe
Text job details to AI
The post tells its reader to provide job details; the person’s role and details are not specified.
- NextAI action in recipe
Ask three questions
The prompt directs AI to ask three questions before drafting; question topics and answers are not reported.
- NextAI draft in recipe
Write a one-page change order
The requested draft states the work, price and date. No actual document or terms were inspected.
- NextSend timing in recipe
Send before the crew starts
The post says to send the draft before work begins. It does not say who signs or receives it, or establish signed acceptance.
What the source reports
Ken Reiners (@Ken_LinkWell) warns contractors against doing extra work before anyone signs. His recipe has a person text job details to AI; the prompt asks three questions and then drafts a one-page change order stating the work, price and date. The post says to send it before the crew starts. It does not name who answers the questions, receives or signs the order, establish that work waits for a signature, or report that this recipe was used.
Source accounts: @Ken_LinkWell
Reported technology: Ken Reiners @Ken_LinkWell; AI tool unspecified. Scope and outcomes are source-reported.
What the enterprise environment would need
The following is a proposed project design for an enterprise doing similar work. Published details are marked; the remaining systems, data and scenarios would be agreed for your project.
Proposed practice environment
Rehearse a change-order draft against agreed job terms
Illustrative project design to scope with your enterprise.
Checks designed, not executed. Domain owners must agree the reference results, permissions and acceptance tests before implementation.
- 1 · Set up the environment
Fixed job facts and an approved reference
Domain owners agree fictional scope, price, date, revision and authorized-signatory fixtures before any test.
- 2 · Project lead and bounded drafting agent
Clarify and prepare a draft-only order
The agent asks for missing fields and drafts work, price and date from the fixture. No live contract or customer message is available.
- 3 · Independent checks
Compare terms independently
A separate checker compares each field and version to the agreed scope/price reference. Missing or conflicting terms fail. Checks designed, not executed.
- 4 · People decide acceptance
Commercial owner reviews the checked pack
An accountable owner accepts or rejects only the exact rehearsal evidence and confirms who may sign in any later live process.
A reviewable evidence package
Versioned fictional change-order draft, field-level comparison, unresolved questions and bounded owner decision.
If a check fails → withhold acceptance.
A price conflicts with the approved reference or the scope revision is stale. Hold acceptance, repair the draft and evidence, rerun independent checks, then return to owner review.
Failure or owner rejection returns to review
- Hold
- → 2 · Repair draft or reference evidence
- → 3 · Rerun independent checks
- → 4 · Owner review
Operating boundary. Fictional records and draft-only writes. No customer contact, live signature, contract update, dispatch or crew work. Domain authority and references require owner agreement. Checks designed, not executed.
- Systems and tools
- Published: an AI drafting step, with the tool unspecified. Proposed: use a fictional job record, approved scope/price reference and draft-only store; do not connect a real customer, contract or dispatch system.
- Data and state
- Proposed: version job scope, quantities, price, date, clarification answers, source reference and draft state. The post does not identify a rate card, contract template, signer or signature record.
- People and handoffs
- Published: a person sends job details and the post says to send the resulting draft before the crew starts; exact roles and recipient are unstated. Proposed: a project lead supplies fixture details, an independent checker verifies the draft and an authorized commercial owner reviews the exact evidence.
- Rules and authority
- Published: the author warns against extra work before anyone signs and says to send the draft before the crew starts; the signatory and completed-signature gate are not specified. Proposed: keep all work fictional and require domain owners to define who can sign before any live process is considered.
- Normal and exception cases
- Proposed: design complete, missing, conflicting and stale scope/price/date cases; hold mismatches and unauthorized actions. No source test result is reported.
- Reset and replay
- Proposed: restore the same versioned job fixture and reference, retain failed checks, repair the draft and rerun independent checks before owner review. No source reset or replay is described.
A proposed simulation
An illustrative practice design derived from this work, not an executed assessment.
Proposed: prepare a traceable fictional change-order draft and evidence pack for independent checking and an authorized owner decision.
Review gate: Proposed: after domain agreement on scope, price, signatory and permissions, an owner reviews only the exact independently checked draft. Acceptance of a rehearsal does not authorize sending, signature or crew work.
Challenge the result: Proposed: omit the price or introduce a conflicting scope revision. The independent check must fail and hold acceptance; repair, rerun checks and return to owner review.
What needs checking
- Proposed: compare every work, price and date field to a separately agreed job reference; do not use the drafting agent as its own verifier.
- Proposed: missing or conflicting terms hold the draft for clarification. Verify the exact draft version and prevent mock send or work-start state changes.
- Proposed: owner acceptance applies only to the checked rehearsal pack. Failed checks or owner rejection return through repair, independent rechecks and a renewed owner decision. Checks designed, not executed.
Review environment fidelity, human capability and agent performance separately. The enterprise’s accountable owners decide acceptance of the shared workflow and any operating use.
Questions about this example
- What does Ken Reiners’ change-order recipe describe?
- The post directs a person to text job details to AI, have it ask three questions and draft a one-page change order with work, price and date, then send it before the crew starts.
- Does the post say who signs the change order?
- No. It warns against doing extra work before anyone signs, but does not identify the signer, recipient or an enforceable signature gate.
- Is this an implemented contractor workflow?
- The post is an instructional recipe. No named contractor, executed document, customer acceptance, signature or operating result is reported.
- What would a similar enterprise test need?
- A proposed fictional job fixture, separate scope/price reference, draft-only environment, independent field checks and an owner decision. These checks are designed, not executed, and require domain agreement.
Shape this around your enterprise
Bring a similar workflow and the people responsible for it. Together, define the records and systems to use, the result your team will build or configure, and how its owners will check it. Nuvepro scopes the simulation, environment and preparation. Agree any existing-agent evaluation, implementation assistance and production responsibilities separately.
Sources and limitations
Curation review: . This is the date this source example was reviewed, separate from source publication dates.
- This is a practitioner recipe, not an observed contractor workflow or named customer case. No execution, signature, customer acceptance or result is reported.
- The source specifies three questions and draft fields for work, price and date, but does not specify the questions, recipient, signatory, contract authority or an enforceable work-start hold.
- The AI product, pricing source, job records and change-order document were not identified or inspected.
- The fictional environment, references, permission boundary and checks are proposed. Domain-owner agreement is pending; the environment has not been built or run.
- Ken Reiners on drafting contractor change orders before work beginsSource publication: 2026-11-10