Project Cost Overrun Review
Find where a project budget drifted.
Added October 15, 2026. Written with AI assistance and checked for clarity and placeholders; not reviewed by a lawyer, accountant, clinician or other professional. How these prompts are made
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it (what [VERIFY] means).
Review a project cost overrun. Original budget, changes approved, actual spending by category and timeline: [PROJECT_COSTS]. Change requests and reasons: [CHANGES]. Contracts involved: [CONTRACTS]. Trace the overrun by category and period, separate approved changes from unapproved ones, estimate how much came from scope, price, time and error, and check forecasts made during the project against outcomes. Return a table with Category, Budget, Actual, Variance and Cause, a timeline of when the overrun became visible, and controls that would have raised the alarm earlier. Contract terms are [VERIFY] with a professional. Also suggest early warning indicators, such as cost per milestone against plan, and a rule that any forecast over a set percentage triggers a formal review. Use only the figures I supply, mark estimates as estimates, and flag anything that depends on accounting standards or tax rules [VERIFY] with [JURISDICTION] for an accountant to confirm. Close by suggesting a small experiment I can run in the next two weeks to test the most uncertain recommendation before committing to a larger change.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.