Amendments

Structured amendment workflow tied to design CRs, with rate negotiation against historical comparables and automated SAP updates.

What it is

Amendments arise from design changes, scope variations, or rate escalations. Today they are handled ad-hoc — vendor does the work, bill comes in, CPT cannot tell if it is scope creep or genuine amendment. The module structures the workflow: quantification of impact, rate negotiation with comparable history, SAP update automated, vendor notification. Bill flow does not get held up by amendment limbo.

Inputs

Triggers

·Design CR approved in M12
·Site reality variance flagged by CM
·Vendor scope or rate amendment request
·BOQ recompute triggered by drawing change in M10
·Budget variance threshold breach in M11

Data reads

·Original WO terms from M14
·Updated BOQ from M10
·Historical amendment patterns and negotiated rates
·Budget impact from M11
·CR impact assessment from M12

Artefacts consumed

·Amendment request with reason and scope impact
·Original WO and prior amendments
·Updated drawings and specifications
·Rate negotiation correspondence

Tools & Techniques

Methods

·Structured amendment workflow tied to source trigger (CR, scope, rate)
·Impact quantification by DCO — quantities, schedule, cost
·Rate negotiation with historical comparables surfaced
·SAP WO amendment auto-updated on approval
·Bill workflow synchronisation — no held-up bills due to pending amendments

Policies

·amendment policy with approval thresholds
·Rate negotiation policy with historical-comparable benchmarks
·SAP synchronisation policy

Decision rules

·Every amendment traces to a source trigger
·Impact quantification mandatory before negotiation
·Amendment approval threshold cascades from CPT to CPT Head to Director
·SAP sync mandatory before bill workflow proceeds against amendment

Outputs

Artefacts produced

·Amendment ticket per change
·Quantification report with impact across cost, schedule, scope
·Rate negotiation history
·SAP amendment record
·Vendor notification of revised scope

Data writes

·WO updated in SAP and Bandhoo
·Budget commitment updated in M11
·Vendor engagement updated in Vendor 360

Downstream triggers

·SAP-updated WO unlocks bill workflow in M21
·Vendor notification with revised scope
·Budget commitment update may trigger variance alert in M11

Stakeholders

CMTriggers amendment from site reality
VendorRequests amendment with scope or rate
DCOQuantifies impact
CPTNegotiates rate, approves amendment
FinanceSAP commitment update
CPT HeadApproval

The flow

01Amendment request raised — design CR, scope, or rate trigger
02Quantification of impact by DCO
03Rate negotiation against historical comparables
04SAP WO amendment
05CPT Head approval
06Vendor notification

State change

Before

Amendments handled case-by-case; SAP updates lag; bill flow stuck.

After

Amendments are tracked tickets; SAP synced; bill flow not held hostage.

Real-world example

Worli — design CR #2208 (slab opening change) approved on 13 May. BOQ recalculated 14 May, variance +₹2.1 Cr. Rate negotiated at +3% over comparable amendments. CPT Head approves at 12:12 PM. SAP updated. Vendor notified by end of day. 34 amendments YTD across portfolio, total ₹12.6 Cr.

Artefacts

·Amendment ticket
·Quantification report
·Rate negotiation history
·SAP amendment record
·Approval log

Pain today

Vendor does work beyond WO; bill arrives; CPT cannot tell if scope creep or genuine. SAP not updated. Payment held. Rate escalation requests are case-by-case with no comparable data.

Integrations

BandhooSAP