The monthly scope stays fixed while unresolved project decisions enter the support queue.
Illustrative scenario. The situation and arithmetic below explain a delivery pattern. They are not a reported interview or a client result.
A service-name change arrives beside the routine website updates, but publishing it requires a decision about the catalogue, an amendment to the enquiry form and confirmation that the sales team uses the same name in its records.
It looks like another update.
Keeping the agency involved after launch gives the client a team that knows the platform and can make small changes without restarting procurement each time a page, campaign or customer-facing detail needs attention during normal operations.
That continuity has real value.
The account director gathers the missing answers because sending the request back would delay the client and leave the delivery team waiting, particularly when the people authorised to decide are spread across departments with different priorities.
Someone has to connect them.
Suppose a monthly agreement allows 40 delivery hours and eight requests each require two additional hours of clarification; those 16 hours consume 40 percent of the allowance before the requested changes themselves have been completed.
This is an illustrative ledger.
Procurement terms, internal approvals and changing campaign dates can all slow decisions, while the person requesting the work may have no authority to change those processes or establish ownership across the departments affected by a single update.
The delay can be understandable.
When a maintenance request also requires the agency to settle the client’s operating decisions, the retainer absorbs work beyond the published change; without a separate scope or allocation, each reasonable intervention consumes the same fixed allowance.
The retainer is funding decisions that its scope never named.