# Change Order Impact MCP > Change Order Impact Calculator quantifies exactly how scope creep hits your bottom line. This MCP helps construction and project managers track the total cost and schedule consequences when changes happen. It moves beyond simple add-ons, giving you a clear picture of cumulative financial risk and project timeline drift. ## Overview - **Category:** finance - **Price:** Free - **Tags:** construction, scope-creep, change-order, cost-control, risk-management ## Description Scope creep is a killer in construction. When a client asks for one small change, it usually triggers a cascade of unexpected costs and delays. This MCP gives you the tools to manage that mess. Instead of guessing or relying on gut feeling, your AI client runs the numbers for you. You can figure out the price impact of any single scope adjustment by applying overhead and profit margins to direct costs. If you're dealing with multiple changes over time, you track how they pile up using cumulative tracking. Plus, you get an immediate risk assessment that tells you if the project has drifted into dangerous territory based on total change volume. Just connect Vinkius to your preferred AI client; it handles the complex math so you don't have to. ## Tools ### assess_project_risk_level Categorizes the financial health of a construction project based on the amount of accumulated scope changes. ### calculate_change_order_price Determines the full price charged to a client for one specific change in scope by applying overhead and profit margins. ### calculate_cumulative_impact Calculates the total financial cost and schedule delay when multiple changes have affected an original contract. ## Prompt Examples **Prompt:** ``` Calculate the price for a change order with $5000 direct cost and 20% markup. ``` **Response:** ``` The total change order price is $6,000.00, which includes a markup amount of $1,000.00. ``` **Prompt:** ``` What is the cumulative impact if my original contract was $100,000, I have $15,000 in previous changes, and this new change is $5,000 with a 2-day delay? ``` **Response:** ``` The updated contract value is $120,000.00. The total change order volume is 20% of the original contract, and the estimated project delay is 2 days. ``` **Prompt:** ``` Assess risk for a $50,000 contract with $10,000 in total change orders. ``` **Response:** ``` The project is at medium risk level because the percentage drift is 20.00%. ``` ## Capabilities ### Determine single-change cost Calculate the exact price charged to a client for one specific scope change, factoring in markups. ### Track total project impact Calculate how multiple changes affect both the overall contract value and the project schedule. ### Assess financial risk level Categorize the current financial health of the project based on recorded scope drift volume. ## Use Cases ### The client adds a small feature mid-build A client asks for new electrical wiring. Instead of just adding the material cost, you use calculate_change_order_price to determine the total price impact, making sure overhead and profit are factored in before sending the revised invoice. ### Multiple changes build up over six months Over half a year, various small additions accumulate. You run calculate_cumulative_impact against the original contract value to show the owner exactly how much the total cost and timeline have ballooned due to scope creep. ### Project budget starts looking shaky You suspect that too many small changes are destabilizing the project. Running assess_project_risk_level gives you a clear, objective report showing if the cumulative change volume has pushed the contract into medium or high-risk territory. ## Benefits - Stop guessing on costs. Use calculate_change_order_price to determine the total price impact of any single change by applying overhead and profit margins correctly. - Track budget erosion with confidence. By using calculate_cumulative_impact, you see how multiple changes affect both the overall contract value and the project schedule simultaneously. - Mitigate surprise blowouts. Running assess_project_risk_level helps flag if scope creep has pushed your entire project into a high-risk financial zone. - Save hours in billing. This MCP automates complex, multi-step calculations that typically require spreadsheets, giving you instant professional reports. - Maintain control. You get objective data on project drift, moving conversations from 'it feels expensive' to 'the numbers show X percent over budget.' ## How It Works The bottom line is you get immediate, quantifiable answers about project financial health without manual spreadsheet work. 1. Input the raw data: feed the MCP the original contract value, direct costs for a new change, and any existing cumulative change order volumes. 2. Run the calculation through your AI client, selecting whether you need a single-change price, cumulative impact, or risk assessment. 3. Receive an instant report that clearly states the updated contract value, the total percentage drift, and the estimated timeline adjustment. ## Frequently Asked Questions **How does calculate_change_order_price work?** It figures out the final client price for a single scope change. You feed it direct costs, and it automatically adds your overhead and profit margins to give you the full number. **Can I track multiple changes with calculate_cumulative_impact?** Yes, this is its primary job. It takes all previous change orders into account alongside new ones to provide a total financial and schedule impact report for the entire project history. **What does assess_project_risk_level do?** It reviews the volume of scope creep you've accumulated. It then categorizes your project into low, medium, or high risk based on that cumulative change data. **Is this better than using a dedicated accounting system?** This MCP is designed for quick calculation and assessment. While an accounting system holds the ledger, this tool gives you immediate, actionable insights into financial risk based on project scope changes. **Can I use calculate_cumulative_impact to predict delays?** Yes. When running calculate_cumulative_impact, it estimates the total delay in days caused by all tracked scope changes against your original timeline.