{{project}} / month [ ] / provider {{business}} / priority owner {{contact}}

Purpose: make each requested output schedulable before treating it as included or accepted. Read the actual retainer agreement first: included services, capacity unit, coordination/review treatment, availability, extra work, unused capacity, and approval authority [ ]. Unknown terms need resolution; this kit cannot decide them for you.
Request ID [ ]; received/source [ ]; buyer task and reason [ ]; exact output/quantity [ ]; acceptance check [ ]; requested deadline and external reason [ ]; approver [ ]. Separate a requested date from an accepted date. “Update graphics” needs the number, format, supplied content, and review boundary.
Input readiness: approved copy/data [ ]; source files and rights/status [ ]; required access through approved invitations [ ]; dimensions/receiving requirements [ ]; dependencies/owner/date [ ]. Do not copy passwords, customer records, or unnecessary confidential material into the shared plan.
Estimate: production [ ]; included review [ ]; task coordination already counted elsewhere [ ]; total [ ]; source and uncertainty [ ]. Count each hour once. If the budget is money, points, or outputs rather than hours, use the agreement’s actual unit and do not invent a conversion.
Request register
ID | output and acceptance | ready/blocked and reason | estimated effort | requested date | accepted plan/state
--- | --- | --- | --- | --- | ---
[ID] | [bounded output] | [input/owner] | [unit and range] | [date] | [scheduled/backlog/declined/waiting]
Choose a state: ready for priority decision; blocked on input; needs separate scope; accepted into the plan; backlog not committed; declined with reason. A client sending a request does not automatically create included work or new availability.
Clarification draft: “I have recorded [ID/output]. To schedule it we need [minimum input] from [owner] by [date]. Its current estimate is [effort and uncertainty]. The requested date is [date]; I will confirm a delivery window after inputs and priorities are agreed.”
Ready when someone can estimate, accept, and later check the output without guessing its scope. Keep incomplete work visible without reserving an unsupported deadline.

Your decision
Does each request describe an outcome and deadline?
My answer: [ ]
Source and date: [ ]
Still to check: [ ]
Next action, owner, and due date: [ ]

Before you start
- Available hours: [Source or notes]
- Recurring work: [Source or notes]
- New requests: [Source or notes]

What you will make
An agreed monthly priority plan with visible capacity and tradeoffs.