Home Renovation Change Order Log

Overview

Helps homeowners track change orders during a renovation or remodel project. When a contractor proposes a scope change, this skill guides the user to document the request, reason, cost impact, timeline effect, approval status, and any unresolved questions — creating a shared log that prevents "I thought that was included" disputes.

When to Use

Use this skill when the user asks to:

• log a renovation change order
• track contractor change requests
• document a remodel scope change
• keep a record of construction changes and their costs
• organize renovation approvals and open questions

Trigger keywords: renovation change order, contractor change log, remodel scope change, construction change record, home project tracker, renovation budget, change order, contractor extra, scope creep

Required Inputs

• Description of the proposed change (what is being added, removed, or modified)
• The reason for the change (unforeseen condition, owner preference, code requirement, etc.)
• The contractor's quote or estimate for the change (cost, materials, labor)
• The timeline impact (additional days, sequencing changes, dependencies)
• The current project context (original scope, budget, schedule)

Workflow

1. Capture the change request. Ask the user to describe the change clearly, including who proposed it and when.
2. Document the reason. Clarify why the change is being considered: owner request, unforeseen condition, inspection requirement, design refinement, etc.
3. Record the quote delta. Prompt for the cost breakdown: labor, materials, permits, and whether it is fixed-price or time-and-materials.
4. Assess timeline impact. Note how many days the change adds, whether it affects other work, and any sequencing dependencies.
5. Track approval status. Create fields for: proposed date, approved/rejected/pending, who approved, approval date, and any conditions.
6. Log open questions. List any unknowns the contractor still needs to clarify before the user can decide.
7. Summarize the log. Present a running change order log entry that the user can keep and share with the contractor for mutual confirmation.

Output Format

The output includes:

1. Change order log entry (single, structured record per change)
2. Cost comparison (original scope cost vs. change cost — user-supplied only)
3. Timeline impact summary
4. Approval tracker (status, date, person, conditions)
5. Open questions list
6. Running cumulative summary (if multiple changes are logged)
7. Safety notes and disclaimers

Safety & Compliance

Explicit Boundaries

• No legal advice. This skill helps document changes and organize communication; it does not interpret contracts, lien laws, or construction regulations.
• No construction, engineering, or technical advice. The skill does not assess the necessity, safety, or technical feasibility of any change. All construction decisions must be made by qualified professionals.
• No permitting or code advice. The skill does not determine whether a change requires a permit or meets building codes. Users must consult their contractor and local building authority.
• No safety assessments. The skill does not evaluate whether a change is structurally safe, fire-safe, or otherwise code-compliant.
• No cost estimates or valuations. The skill does not estimate reasonable costs, assess fairness of quotes, or project final project value. Users must obtain and evaluate quotes from their contractor or additional professionals.
• Written confirmation recommended. The skill encourages the user to obtain written confirmation of all change orders and to have high-risk structural, electrical, plumbing, or load-bearing changes reviewed by a licensed professional before approval.
• No account or payment handling. The skill does not process, store, or advise on payments, deposits, or financing.

Additional Safety Notes

• This is a descriptive prompt-flow skill with zero code execution, zero network calls, and zero credential requirements.
• Content is intended to help users maintain organized records and clear communication with contractors.
• The user remains fully responsible for construction decisions, contractor selection, contract terms, permits, inspections, safety, and all financial commitments.

Acceptance Criteria

1. Produces a structured change order log entry with all key fields.
2. Documents the change reason, cost impact, and timeline effect using only user-supplied data.
3. Includes an approval tracker with status and responsible party.
4. Lists open questions that require contractor clarification.
5. Explicitly states that legal, construction, engineering, permitting, and safety advice are not provided.
6. Encourages written confirmation and professional review for high-risk work.

Examples

Example 1: Basic Use

User says: "My contractor just told me we need to replace some rotted subfloor — he quoted $1,200 extra and 2 more days. Help me log this change order."

Skill guides: Capture the change description, reason (unforeseen condition), cost ($1,200), timeline (+2 days), and create the log entry with open questions (e.g., "Is this all the rot, or might more be found?").

Example 2: Detailed Session

User says: "We've had three change orders this week on our kitchen remodel and I'm losing track of the budget impact."

Skill guides: Log each change individually, then present a cumulative running summary with original budget, total changes so far, and remaining unresolved items.