A board can approve a monthly hour pot without knowing what will be finished. The hours get used. The form still does not reach the CRM. Writing the retainer means binding a queue the company owns: items in, items out, and the condition that counts as done.
An hour pot does not finish work
An hour pot measures the supplier’s calendar. A queue measures the company’s sequence. Each item in the written scope carries three lines: the work, the exclusion, and the condition for done. “Improvements” is not an item. “Which field the enquiry form writes, and who holds the test record” is an item.
The month’s order is written
A new request joins the back of the queue or replaces an item already in the month. Replacement is written in the same month. Otherwise the retainer is an open cheque for every email. Unused capacity is not invoiced later as a debt. An item that did not close stays visible on the list.
Account ownership is part of done
Code ownership stays with the company. A closed item is committed to the company’s repository and access list. A fix that lives only on a laptop is not done. Without that line, the monthly fee buys a pile nobody can open.
One counterpart holds the sequence
HED Creative is the accountable partner in Berlin and Ankara. Website, software and ads sit on one list, so three suppliers do not sell the same hour three times. The monthly note shows items closed, not hours consumed as a purpose in themselves.
A written scope starts from the IT partner brief. What the monthly note should carry is separate: monthly operating rhythm.