Make the delivery week visible
A prospective client wants to start next month. The recurring fee looks useful, and the work is well within your expertise. The uncomfortable question is whether it fits beside the promises you have already made. Your diary has gaps, but you know those gaps are where preparation and thoughtful implementation happen.
If you run a Bristol operations consultancy with one associate, a monthly revenue total cannot answer that question. You need to see who will do the work, when it needs attention and which commitments can genuinely move. Otherwise another attractive retainer can quietly turn into a permanent late evening.
This guide helps you evaluate that workflow. Gbeya has booking availability logic and an agency economics calculator, but neither establishes a complete retainer allocation system. We will separate those inspected foundations from the planning controls that still need a demonstration. The aim is a defensible decision about the next client, not a fuller-looking calendar.
Can the next retainer fit without displacing a promise?
Use the next four working weeks. Keep client names and sensitive details out of any shared demonstration dataset.
- List each person’s actual working hours and dated absence.
- Subtract known non-delivery commitments once, using a clear classification.
- Place existing retainer work and fixed deadlines against the person who must deliver it.
- State a reserve for uncertain requests and explain the choice.
- Add the proposed retainer in its required delivery window, then inspect the busiest person and week.
If the work only fits by removing an existing commitment or relying on unagreed extra hours, change the proposed scope, timing or staffing before accepting it.
This is an operating decision aid, not an employment-law assessment or a guarantee that estimates match actual work.
Three records, three different questions
Agreement
What work and response commitments have you promised?
Allocation
Who will deliver it, and in which period?
Money
What is billed or paid, independently of available hours?
A planning model, not a demonstration of an implemented retainer allocation system.
1. Translate the retainer into work before allocating it
Start with what the client can actually request. A fixed monthly payment might buy a defined set of deliverables, access to advice, a reserved block of time or a combination. Those are different delivery promises. Your software needs to represent the agreement you have made rather than forcing every retainer into an identical hourly bucket.
Write down routine meetings, preparation, follow-up and the less predictable requests. Assign a named owner and a delivery window to each recurring item. If the promise is deliberately flexible, decide how requests are accepted and prioritised. Flexibility for the client still needs a boundary your team can operate.
- Why this matters
- Billing describes money due. Allocation describes work assigned to someone in a period. Connecting the two can support decisions, but payment alone does not reserve or measure delivery time.
- Work through the example
- Suppose a client pays for a monthly review and ongoing implementation advice. Your initial plan includes two hours for the review, two for preparation and four for follow-up work. Keep the eight-hour estimate separate from the contract and refine it from actual delivery.
- When the usual approach changes
- An outcome-based engagement may have no purchased-hour allowance. Estimating workload can still help you plan internally, but do not present that estimate as a new limit on an agreed client outcome.
- Your decision
- Choose software that keeps contract scope, estimated effort and money separate while letting you connect them. Do not assume recurring billing creates a capacity reservation.
2. Use the hours you can responsibly assign
A working week contains more than client delivery. Business administration, proposals, professional development, preparation and leave all use time. Deduct them explicitly before declaring availability. For your associate, use their actual working arrangement rather than copying your own week.
Keep the denominator visible. When a screen says eighty per cent utilised, ask: eighty per cent of which hours, over which dates, and based on planned work or time already recorded? Two apparently similar percentages can describe very different workloads.
- Why this matters
- Available delivery time is the chosen working capacity after known non-delivery commitments and leave. Scheduled workload is then compared with that same period and person. Changing the denominator changes the percentage without changing the work.
- Work through the example
- Suppose your working week is thirty-five hours and eight are reserved for administration and business development. You have twenty-seven hours before allowing for uncertain requests. An associate with twenty-four working hours and four non-delivery hours has twenty. Do not display either person as having forty hours available.
- When the usual approach changes
- Some non-delivery activity directly supports a client and belongs in that engagement’s effort record. The important thing is consistent classification: neither omit it nor subtract it twice.
- Your decision
- Require editable working patterns, dated leave and a visible calculation. Reject a capacity figure you cannot explain in ordinary hours.
3. Find pressure in the actual week, not the monthly average
Monthly totals can hide a crowded Tuesday or a deadline week. Allocate work to a realistic window and inspect the individual responsible. Your associate may have spare hours while only you can lead a particular client review. That spare time is not automatically interchangeable.
Include preparation and transition time around meetings. A free appointment slot is not necessarily spare consulting capacity. Gbeya’s inspected booking code considers availability, existing bookings and service buffers, but that is narrower than assigning all retainer work across a team.
- Why this matters
- A weekly view exposes competing deadlines and skill constraints that a total cannot show. Buffers protect time adjacent to appointments; they do not automatically account for every report, analysis task or client request.
- Work through the example
- Suppose two clients both need your final review on Thursday. Moving an associate’s administrative task will not solve the clash. You might agree an earlier draft, change a review date or delegate a defined part of the work with the client’s requirements intact.
- When the usual approach changes
- If a service is genuinely interchangeable and can be delivered at any point in the month, a monthly allocation may be sufficient. Do not create daily precision that the work does not justify.
- Your decision
- Use the shortest planning window that reveals the real bottleneck, and assign by person and capability before relying on team totals.
4. Keep a deliberate margin for work you cannot predict
An experienced consultant can estimate routine work and still face a difficult client question, a sick day or a revision that needs more thought. Do not hide that uncertainty inside an unrealistically precise schedule. Leave an explicit margin, then review whether it is suitable for your actual service.
There is no universal utilisation target in this guide. A reactive advisory retainer needs different availability from a tightly scheduled training day. Equally, unused capacity is not automatically waste: it may be the space that allows you to meet a response commitment without disrupting another client.
The reserve is your explicit planning assumption, not a benchmark supplied by research. Review it against dated demand and the response promise you have agreed.
- Why this matters
- Planning uncertain work as though it were fixed transfers the risk into someone’s evenings or into a missed promise. An explicit reserve makes the trade-off visible before you accept another commitment.
- Work through the example
- If your twenty-seven delivery hours include five reserved for unpredictable requests, you can assign twenty-two to known work. A six-hour new commitment does not fit when only four assignable hours remain. Negotiate scope or timing rather than quietly removing the reserve.
- When the usual approach changes
- A highly repeatable service with stable demand may need a smaller reserve. Too much reserve can also make a viable business look artificially full. Adjust from dated experience rather than a general rule.
- Your decision
- State your reserve as a planning choice, record why it exists and review it. Do not sell the same hour as both guaranteed availability and already committed work.
5. Test the decision you need the software to support
Ask for a demonstration with your type of retainer, not a generic tour. The useful question is whether you can see the consequence of a new commitment before you accept it. Start with two people, existing allocations, one planned absence and a client whose deadline moves.
Check what happens when work is cancelled, moved or completed. A cancellation should not remain as active demand, but it should not erase the history needed to understand the month. Keep estimated time, recorded time, billed amounts and collected payments separate. None is a substitute for the others.
- Why this matters
- A capacity model is useful when changes propagate consistently and remain explainable. A warning that ignores leave or counts cancelled work cannot reliably guide your next commitment.
- Work through the example
- Rehearse a six-hour request in a week with four hours available for the required consultant. The system should show the two-hour shortfall, identify that person and period, and preserve the previous plan. Then move the request to a genuinely available week and check the result again.
- When the usual approach changes
- A small practice with stable work may manage this decision adequately in a maintained planning sheet. Replacing it is worthwhile when the proposed workflow improves accuracy, coordination or visibility enough to justify the change.
- Your decision
- Buy or build against observable acceptance checks. Until retainer allocations and warnings are verified in Gbeya, use a documented planning process and request a scoped demonstration rather than assuming the controls exist.
Make room deliberately, then decide
For your Bristol practice, we would start with the work already promised and the person who must deliver it. A team-wide percentage is useful only after those commitments and the available hours are clear.
The argument for fuller utilisation is commercial: unused delivery capacity can limit revenue. The counterargument is operational: a service that promises responsiveness needs some room to respond. Your task is to choose and review that balance, not borrow a universal target.
Professional resource guidance provides the planning framework; employee workload guidance supplies a boundary on agreed demands, and supplier documentation illustrates calculations rather than proving Gbeya capability. The direct owner/associate viewpoint remains a research gap. A maintained planning sheet is the opposing practical option when it already supports a reliable decision.
The five-hour and four-hour reserves in the worked example are assumptions for that planning week. Review them against actual requests; neither the workload guidance nor laboratory task-switching research establishes those amounts.
Gbeya’s inspected booking and economics foundations can inform parts of the discussion. They do not establish a complete retainer planner. Use the diagnostic to request the missing behaviour, verify it with realistic cases and then decide whether the workflow deserves responsibility for your next commitment.
High confidence in the arithmetic and inspected source-code observations only; Medium confidence in the proposed operating method for this practice. Neither establishes live feature readiness.
No client interviews, production allocation tests or measured improvement were obtained. Estimates, legal obligations and individual working arrangements need their own checks.
Capacity decision with stated assumptions
A positive team total can still hide a shortfall
For one planning week, suppose you have thirty-five working hours, eight non-delivery hours and a five-hour reserve. That leaves twenty-two assignable hours. Eighteen are already committed, leaving four. Your associate has twenty-four working hours, four non-delivery hours and a four-hour reserve: sixteen assignable hours. Fourteen are committed, leaving two. The team has six hours unassigned, but a six-hour request requiring your personal delivery exceeds your four available hours by two. Separately, suppose the proposed retainer brings £1,200 per month; the six-hour request belongs to this planning week and is not a statement of its entire monthly obligation; that amount does not remove the two-hour constraint. It is an assumed client fee, not a Gbeya price or observed result.
Both rows and the six-hour request refer to the same planning week. Values are stated assumptions.
Owner: 35 working hours
8 non-delivery + 5 reserve + 18 committed + 4 available = 35 hours.
Associate: 24 working hours
4 non-delivery + 4 reserve + 14 committed + 2 available = 24 hours.
Owner-only request: 6 hours. The owner has 4 available hours, leaving a 2-hour shortfall. The associate’s 2 spare hours do not resolve it unless the work can genuinely be delegated.
Owner: 35 − 8 − 5 − 18 = 4 hours. Associate: 24 − 4 − 4 − 14 = 2 hours. Owner-only request: 6 − 4 = 2 hours short.
The monthly fee is a separate commercial assumption. These bars are proportions of each person’s own week, not equal-duration comparisons.
If two hours can genuinely be delegated and fit the associate’s skills and delivery window, the plan may work. Confirm the handoff and client requirements; do not assume every spare hour is interchangeable.
Inspect the constrained person and period before the team total. Record the commercial case separately from the capacity decision.
Two assumptions worth checking
A recurring payment means the client’s time is reserved.
Billing and allocation are separate records. Verify the connection instead of assuming it.
A free calendar slot means the practice can take more work.
Preparation, analysis, leave and service obligations may already depend on that time.
Your next 30 days
Days 1–7
Make the promises visible
Map current retainers, delivery owners and recurring work without changing client terms.
Ready for the next step: Each commitment has a scope, estimate and delivery window.
Days 8–14
Set a usable baseline
Record working patterns, absence, non-delivery time and a justified reserve; inspect the next four weeks.
Ready for the next step: Every capacity percentage can be explained in hours and dates.
Days 15–21
Rehearse changes
Test a new retainer, moved deadline, cancellation and absence in a safe demonstration.
Ready for the next step: Shortfalls and released capacity are accurate and history is preserved.
Days 22–30
Choose the operating method
Compare the demonstrated workflow with your existing process; build missing controls or retain the reliable method.
Ready for the next step: You can explain the next-client decision without relying on hidden overtime. Thirty days is a review window, not a forced purchase deadline.
Questions before you choose
What is retainer capacity planning?
It compares the work you have promised with the people and time available to deliver it. It is separate from issuing a recurring invoice.
Should I plan retainers in hours if clients buy outcomes?
You can estimate internal effort without converting an outcome agreement into an hourly contract. Keep that distinction explicit.
What utilisation target should I use?
There is no universal target here. Define the denominator, work pattern and reserve appropriate to your service, then review actual experience.
Does Gbeya already allocate retainer hours across a team?
A complete retainer allocation model and over-capacity warning workflow were not verified in this inspection. Request a demonstration against the checks in this guide before relying on them.
Can the agency economics calculator make this decision?
It estimates team-and-software economics from your inputs. It does not allocate client work to named people and weeks or prove that another retainer fits.
What should happen when a client cancels work?
The active allocation should reflect the cancellation while keeping an appropriate history. Billing and contractual consequences need their own review; released time is not automatically a refund.
Sources and further reading
Prepared by Gbeya · Sources reviewed 30 October 2026. Retainer allocation, workload warnings and permissions require separate implementation and verification.