A CTR — Cost·Time·Resource — is a structured request used to price a specific piece of work under an existing master service agreement: what it will cost, how long it will take, and what people and equipment it requires. It is how energy, engineering, and construction organisations turn a framework contract into an actual, priced scope of work.
Where CTRs fit in the contract lifecycle
A master agreement fixes the commercial framework — rates, terms, categories — but not the work itself. Each project then calls work off against it. The CTR is that call-off's pricing instrument: the buyer defines scope and deadline, invited suppliers respond with cost, schedule, and resourcing, and the award goes to the best value response within the agreement's terms.
Why the email version fails
Run over email, a CTR cycle takes weeks: scope descriptions vary per recipient, responses arrive in incompatible formats, clarifications fork into private threads, and the comparison is rebuilt by hand in a spreadsheet with no trail of who offered what, when. For organisations running dozens of concurrent call-offs, the administrative drag alone delays project starts.
What belongs in a well-formed CTR
The name is the checklist. Cost: rates for each element of the work, priced in the master agreement’s own terms so responses are comparable and compliant by construction. Time: execution period, milestones, and the response deadline — with late submissions excluded by rule rather than by argument. Resource: the people, equipment, and materials the work requires, specified tightly enough that a thin response is visible as thin. A CTR that pins all three converts supplier responses from prose into data; one that leaves any of them loose reopens the negotiation the master agreement was supposed to have closed.
Scope discipline matters as much as structure. The single most common failure is the scope-of-work paragraph that differs slightly per recipient — usually because it was retyped per email — which makes every response technically non-comparable and gives the eventual audit nothing solid to stand on. Issuing one structured request to all invited suppliers simultaneously, from one system of record, removes the failure mode entirely.
What a structured CTR process changes
In dmp's Contract Management module, a CTR is created against the governing agreement and its pricebook, so responses are priced in the contract's own terms from the start. Every supplier sees only its own request — confidentiality is enforced by the system, not by discipline — and responses land in one comparable structure covering cost, schedule, and resourcing, with the full exchange on an auditable record. The negotiation still happens; it just happens on structured ground, in days rather than weeks.
The takeaway: if your teams price call-offs by email, the master agreement is only half-implemented. The CTR is where its value is either captured or leaked.