AI Automation Prompt: Change Order – Draft Client Scope and Justification

Write two parts: (1) a Scope of Work describing what is changing, derived from the revenue budget lines; and (2) a brief Justification explaining why the change is required, framed for the client. You may reference the revenue line amounts and the revised contract value, because the client sees these. You must NOT mention cost, supplier/commitment values, markup or margin under any circumstances.

- Change order description (existing short title, for context): ((Document.Description))

- Revenue change total (increase/decrease to the contract): ((Document.RevenueChangeTotal))

- Revised revenue total (new contract value for this CO): ((Document.RevenueTotal))

Revenue budget lines (iterate every line — these are the client-billable items).

<div data-foreach-view="RevenueBudget">

- Line description: ((RevenueBudget.Description))

- Quantity: ((RevenueBudget.Qty)) ((RevenueBudget.UOM))

- Line amount: ((RevenueBudget.Amount))

- Revised line amount: ((RevenueBudget.RevisedAmount)) </div>

Constraints:

- Use ONLY the fields above. Never output or infer cost, commitment, markup or margin.

- Write the Scope of Work as clear professional prose or a short ordered list of the changed work items, derived from the revenue line descriptions.

- The Justification must PARAPHRASE ONLY the change order's own recorded description/reason (((Document.Description))) — keep it to 1–3 sentences, client-appropriate and non-defensive. Do NOT assert contractual positions or add rationale that is not in the data: never state or imply that work is "outside the original scope", "unforeseen", a result of errors/omissions, or required "to maintain programme", "avoid delay" or "for compliance" unless those exact reasons appear in the supplied text. If no reason is supplied, write a single factual sentence about the revenue change and nothing more.

- Do not fabricate amounts, items or reasons not present in the data. Terse in → terse out: a short recorded reason stays a short phrase; never expand it into a contractual narrative.

Generate the following and return it in the output fields:

1. @((Document.Text))(string): The full client-facing scope-and-justification narrative as HTML (the Details field is a rich-text/HTML field). Use a "Scope of Work" heading and a "Justification" heading, with paragraphs and, where helpful, a bulleted or numbered list of changed work items. Plain, clean HTML (h-tags, p, ul/ol/li) — no inline styles needed. Revenue/contract amounts are permitted; cost, commitment, markup and margin are forbidden.

2. @((Document.Description))(string): A single-line summary of the change (max 256 characters), plain text, suitable as the change order title. No cost/margin figures.

{

"((Document.Text))": "<h3>Scope of Work</h3><p>This change order covers the following variation items:</p><ul><li>Upgraded glazing to the north elevation</li><li>Additional electrical rough-in to meeting rooms</li></ul><h3>Justification</h3><p>This change is raised to cover the items listed above, as recorded on this change order, and adjusts the contract revenue accordingly.</p><p>Revised contract value for this change order: $42,500.00.</p>", "((Document.Description))": "Ground-floor fit-out variation: upgraded glazing and additional electrical rough-in"

}

## Important Note:

Return ONLY a valid JSON object with exactly the two keys shown above and no other keys. No commentary, no explanation, no markdown code fences. PMChangeOrder.Text must be valid HTML; PMChangeOrder.Description must be plain text no longer than 256 characters. Under no circumstances include internal cost, commitment, supplier, markup or margin figures in either field, matching the constraints in the Instructions tab.