# DenQAI: startup change control ledger

File-specific companion · 2026-09-10

## Purpose

What will a proposed change cost across construction, equipment, schedule, and reserve?

**Who:** Project owner, architect, contractor, and financial reviewer

**Records:** Change proposal; drawing/specification; direct/downstream estimates; delay and permit effects; current contingency.

## Complete the file

1. Assign change_id, reason, controlling_record, and draft status before a decision.
2. Separate direct_cost, downstream_cost, delay_days, and equipment/permit/operating effects.
3. Record contingency_before and contingency_after with a documented reconciliation, owner_role, decision, and recheck.

## Definitions

- **Direct cost:** Cost stated for the change itself.
- **Downstream cost:** Additional effect on other work caused by the change.
- **Contingency after:** Remaining contingency after the reviewed treatment of the change.

## Fictional example

Fictional example: CO-002 adds $8,000 electrical work and $2,000 downstream finish repair; permit timing is still unverified, so approval status remains Draft.

## Review and next action

Decide the change using the complete supported effect and update dependent budgets and dates.

This CSV does not calculate reserve, authorize a change order, or determine schedule impact. Avoid repeating the same cost in direct and downstream fields.

[Related DenQAI guide](https://denqai.com/startup)

## AI coach prompt

Help me use DenQAI’s startup change control ledger. My question is: What will a proposed change cost across construction, equipment, schedule, and reserve? Explain these terms in plain language: Direct cost, Downstream cost, Contingency after. Ask one question at a time about the required records: Change proposal; drawing/specification; direct/downstream estimates; delay and permit effects; current contingency. Walk through the supplied fictional example before asking me for inputs. Treat every missing value as unknown, not zero. Do not invent source records, contract terms, legal conclusions, or clinical facts. Use only permitted fictional or aggregate, non-identifying information. Follow this boundary: This CSV does not calculate reserve, authorize a change order, or determine schedule impact. Avoid repeating the same cost in direct and downstream fields. End with the missing evidence and this next step: Decide the change using the complete supported effect and update dependent budgets and dates.

## AI review prompt

Review my permitted fictional or aggregate draft of DenQAI’s startup change control ledger against the file instructions. Check each required field and period, units, evidence locator, assumptions, arithmetic where formulas are actually supplied, and unresolved contradictions. Check the sequence: Assign change_id, reason, controlling_record, and draft status before a decision. Separate direct_cost, downstream_cost, delay_days, and equipment/permit/operating effects. Record contingency_before and contingency_after with a documented reconciliation, owner_role, decision, and recheck. Separate facts from assumptions and missing records. Do not supply unsupported numbers or make a professional decision for me. Apply this limitation: This CSV does not calculate reserve, authorize a change order, or determine schedule impact. Avoid repeating the same cost in direct and downstream fields. Return corrections, questions for the responsible reviewer, and the next action.