Scope Drift Ledger

Scope Drift Ledger treats every roadmap change as a booked entry rather than a conversation: each new client ask gets logged with the delivery days it displaces and the retainer value it puts at risk. The framework matters because agencies lose margin quietly, not dramatically. A feature moved from next quarter to this one rarely arrives alone; it pushes testing, QA, and launch support into the same window, and nobody invoices for the reshuffle. Keeping the ledger visible turns that invisible cost into a negotiation artifact. ProdPad's Now-Next-Later structure gives the ledger its columns, since items parked in Next can be repriced when a client pulls them forward. Productboard's feedback centralization supplies the demand-side evidence for why an item moved at all. Project Echo's public changelog closes the loop by showing clients what actually shipped against what was promised. Run the ledger for one quarter and the pattern becomes obvious: most drift originates from three or four clients, and those are the accounts where retainer terms need rewriting.