Construction: Change Order Audit with Claude Code: Result JSON Schema

A production playbook for change order audit in construction operations using Claude Code: result json schema, run-scoped inputs, logs, typed results, and artifacts.

Audience: Construction finance and project controls teams

The problem

Construction finance and project controls teams need change order audit to run repeatedly against change orders, contracts, invoices, schedules, and field reports. In construction operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.

Implementation path

Define the outer result contract once, let the change order audit skill own body.data, and reject terminal output that does not match the expected schema.

Tradeoffs and failure modes

Schema enforcement adds upfront design work, but removes prompt parsing from the product surface. For change order audit, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.

Result shape

{
  "schema_version": "argo.result.v1",
  "summary": "change order audit completed",
  "body": { "type": "construction_change_order_audit", "data": {}, "exceptions": [] },
  "artifacts": []
}

Run this on Argo