Calculate Research Capacity Before Promising Dates
Estimate research delivery by available work time, rework, contingency and role bottlenecks rather than multiplying headcount by nominal hours.
10/24/20263 min read
A team promises thirty reviewed account briefs by Friday because the total estimated work seems to fit the available hours. The researchers finish their drafts, but the only reviewer cannot clear the queue in time. A delivery estimate needs more than a headcount multiplied by a nominal working week.
Calculate capacity by completed output and constrained role. Separate time for new work, known rework, fixed responsibilities and contingency. Then check the dependencies that can prevent a brief from being accepted even when someone has time to write it.
Define the deliverable and its stages
State what counts as one finished unit: for example, an account brief with required evidence, explicit unknowns and reviewer acceptance. A row created in a spreadsheet is not equivalent to that deliverable. Identify research, review, correction and handoff steps so the estimate does not stop at draft production.
Use observed work records where available, and label planning assumptions where they are not. W3C describes provenance through information origins. Keeping each input's source visible helps a colleague challenge the estimate. The capacity model itself is an editorial proposal, not a benchmark established by W3C.
A fictional role-constrained worksheet
All numbers below are invented to show the calculation. They are not promised turnaround times or measured productivity for a real team.
Total scheduled team time: forty hours during the proposed delivery window.
Fixed responsibilities: eight hours already committed to other work, leaving thirty-two.
Rework reserve: six hours for existing correction obligations, leaving twenty-six.
Contingency: four hours kept uncommitted for uncertain interruptions, leaving twenty-two hours for new briefs.
Available research allocation: fourteen of those hours, with a planning assumption of thirty minutes per brief. Research capacity is twenty-eight briefs.
Available review allocation: eight hours, with a planning assumption of fifteen minutes per brief. Review capacity is thirty-two briefs.
Completed-output ceiling under these assumptions: twenty-eight briefs, limited by research capacity, not twenty-nine obtained by dividing total hours by forty-five minutes.
Twenty-eight briefs would use fourteen research hours and seven review hours. The remaining review hour does not create additional research capacity unless an authorized, capable person can genuinely perform that work. Treating all hours as interchangeable would overstate the plan.
Keep reserves distinct
Known rework is already expected work, not an optional buffer that can be removed to make a deadline fit. Contingency covers uncertainty and should have a stated purpose. Avoid counting the same reserve twice, but do not hide both inside an unexplained productivity percentage.
If the estimate relies on unusually clean inputs, identify that condition. Ambiguous entities, missing source access or specialist questions can change the task duration. A delivery promise should state the scope it covers and the route for exceptions rather than assuming every record is the easiest case.
Check sequencing before committing
Hours available late on Friday may not help when customer clarification is needed on Wednesday. Map the order of intake, research, review and acceptance. Identify external dependencies and which person can resolve them. Do not turn an unanswered customer question into an assumed same-day response.
A useful estimate can offer a smaller initial batch, a later date or a phased handoff if those options meet the recipient's needs. It should not silently remove review or reduce evidence quality to preserve the original quantity.
Re-estimate when the evidence changes
Compare actual completed work with the assumptions during delivery. If research takes longer because the scope changed, revise the remaining estimate and explain the cause. Do not wait until the promised date to disclose a constraint already visible in the queue.
Keep the final commitment separate from the planning worksheet. The worksheet supports a decision; the authorized owner must confirm the actual scope and date. Honest capacity planning ends with a feasible deliverable and visible limits, not a larger number that depends on treating every person's time as spare, interchangeable and interruption-free.
Sources and scope
The worked examples and decision tools are original editorial proposals, not reported customer results. References support the identified context, not endorsement or validation of these methods.