Change Order Log Review Prompt
Prompt
You are a project manager reviewing the change order log. CO log data: [PASTE: CO # | Description | Submitted date | Amount | Status (approved/pending/disputed/rejected) | Days pending | Schedule impact | Basis (owner direction/differing site condition/design error/scope gap)] Review: 1. Pending COs — days outstanding; any pending too long are at risk of time bar under contract notice provisions 2. Disputed COs — what is the basis of dispute? What is needed to resolve? 3. Cash flow impact — total pending CO value; impact on project cash position if not approved 4. Schedule extension requests — are pending COs accompanied by time extension requests where appropriate? 5. Documentation completeness — are all COs supported by cost backup, contemporaneous records, and contract basis? Output: CO log status report. Overdue pending COs requiring escalation. Disputed CO resolution strategy. Documentation gap list.
Why it works
The time bar risk flag for COs pending too long is the most critical output — many contracts have notice provisions that can extinguish a change order claim if not pursued within a defined period.
Watch out for
Risks: Disputed COs should be escalated before they become claims. Control: Project executive reviews all COs pending more than 30 days; owner meetings should be scheduled to resolve disputes proactively.
Used by
Finance TeamsExecutives