Every active job has the same grind. Change orders come in from all sides, PCOs stall, and someone has to square cost, time, and who pays. The log you used last week is already out of date. The problem is not the math. It is the constant reformatting and rollups to keep the contract sum, contingency, and completion date current. This replaces the weekly rebuild with a register you can rely on. Development ~10 min to run Build Change Order Log Vic prompt Use Vic to build a change order log for an active construction project with current COs and pending PCOs Purpose Keeps contract sum, contingency burn, and schedule exposure current without manual spreadsheet work. A 60-minute manual update drops to roughly 10 minutes. Inputs Change Orders Optional Contract Sum Optional Contingency Optional Schedule Optional Outputs An .xlsx change-order log with one row per CO or pending PCO plus summary totals for contract sum, contingency, and completion date. Time saved Turns roughly an hour of manual work into about ten minutes. How it works Give Vic whatever you have: a list of change orders or pending PCOs, the current contract sum or GMP, the contingency, and any schedule inputs. Clean or messy is fine. Vic builds an Excel change order log with one row per item and consistent fields across the file. Run it with: "Use Vic to build a change order log for an active construction project with current COs and pending PCOs". Each row covers what you need without hopping between tabs: number, description, originator, pricing basis, cost, schedule day impact, funding source, approval authority, and status. Pending items sit next to approved COs so you see exposure, not just what is signed. The file totals the numbers that drive your weekly check-in. You get the revised contract sum or GMP, approved versus pending totals, contingency drawn and remaining with a clear burn signal, and a revised completion date based on recorded schedule impacts. It is the view most teams end up building by hand, without the drift that creeps in after a few edits. This is not about a prettier spreadsheet. It is about a current one. When a new PCO lands or a CO is approved, regenerate the register in minutes and send a clean file to the team. Cost and schedule stay aligned with what is happening in the field. There is a discipline effect too. With every item in the same fields, gaps show up fast. Missing pricing basis, unclear funding source, or an unquantified schedule impact stand out. Items move from PCO to approved CO with fewer loose ends. For development managers and owner reps, this becomes the working log for OAC meetings and lender updates. The contract sum, contingency position, and completion date all tie back to the same rows. No side calculations, no separate trackers that drift. The time savings are real but secondary. An update that takes about an hour drops to roughly ten minutes. The bigger gain is frequency. You can refresh it as often as needed, which means fewer surprises when totals move. You still handle negotiation and approvals. This keeps the register current, consistent, and ready to send.