People Management
Build a Headcount Request Around the Work That Cannot Be Covered
A fictional engineering manager compares uncovered work with reprioritization, process changes, temporary support, and a permanent hire, then checks low/base/high demand and ramp assumptions.
Build a headcount request around the recurring work your current team cannot cover, the business consequence of leaving it uncovered, and the alternatives available to the decision owner. Compare demand with usable capacity for the same work and period, name uncertain assumptions, and allow for hiring and ramp time. Ask for a specific resource decision rather than treating “we are busy” or a preferred team size as proof that a permanent hire is necessary.
This LandOffer.ai guide includes a completed engineering resource request and a low/base/high sensitivity example. All people, work volumes, hours, costs, and responses are fictional planning assumptions, not market salary data or measured productivity. Primary sources were checked October 27, 2026. No position, budget, recruiting process, contractor engagement, or employee assignment was created or approved. A clear case makes the choice reviewable; it does not guarantee hiring approval or financial returns.

Define the work gap before naming the role
Start with the work the organization has asked you to deliver. Group it into continuing service, maintenance, and planned changes so reviewers can see what is recurring and what may be temporary. Identify the time window and the source of each assumption. An observed number of requests is different from an estimate of the effort each request needs, and both differ from a forecast of next quarter’s demand.
Then calculate usable capacity for the same period. Do not multiply each employee by all paid hours and assume every hour is available for the queue. Account for meetings, leave, training, coordination, existing commitments, and the skills the work requires. Avoid subtracting the same obligation twice or quietly making overtime the permanent base case. A shortage of specialist coverage may remain even if the team’s total hours look sufficient.
Describe the consequence in terms you can support. A dated backlog, an unstarted integration, or recurring deferral of maintenance is more useful than an invented revenue-loss figure. If a financial consequence has not been measured, say so. The request can explain the trade-off without pretending that every uncovered hour equals a lost sale.
Recruitment firm Morgan McKinley’s guidance recommends showing evidence of business need and considering workflow changes, reprioritization, automation, or temporary support. Treat this as practitioner guidance, not independent proof that a hire is right for your team. The point is to make competing options visible before a permanent commitment is made.
Make the decision route explicit
Find out who can approve the position, funding, role scope, and timing. A supportive director may still need Finance and People approval. A budget line may not mean permission to open a requisition. A vacancy can require a new decision instead of automatic backfill. Preserve those distinctions in the request and in any later summary of the decision.
GitLab’s current engineering handbook provides a named example: its budgeted headcount review involves Engineering Leadership, Talent Acquisition, Finance Business Partners, and People Business Partners. It also describes backfill decisions to open, close, or repurpose a position. That is GitLab’s process, not a universal approval chain to copy into your company.
The University of Wisconsin–Madison School of Human Ecology’s position-request guide similarly separates an initial position proposal from later detailed recruitment materials. It asks for the business need, key duties, and budget and operational impacts, with title development handled through the relevant process. This supports writing a resource case before drafting an entire interview funnel or choosing a preferred candidate.
Request the individual-contributor capability the uncovered work needs; discuss your own promotion separately. You can explain the supervision or onboarding support required without arguing that you deserve more direct reports. Define the work and necessary capability first; have HR and the relevant owners assess level, title, employment arrangement, and cost through their actual process.
Completed request: recurring support competes with planned engineering work
Ramon manages a two-engineer integration-support team at fictional Bayfield Software. His October 27, 2026, request concerns connector troubleshooting and test infrastructure, not sales hiring or a manager’s span of control. The following four-week record and forecast are invented for this article. They do not establish a real organization’s staffing standard.
The example’s intake record lists 72 support cases over four weeks, or 18 per week on average. Ramon uses two hours per case as a planning assumption, not a measured service-time average. He forecasts 12 weekly hours for test-infrastructure maintenance and 18 for already requested integration changes. Each current engineer has 24 usable hours weekly for these three categories after other obligations, for 48 total. Those deductions are already accounted for and are not subtracted again.
| Work category | Basis in the fictional case | Weekly planning demand |
|---|---|---|
| Connector support | 18 cases × estimated 2 hours | 36 hours |
| Test-infrastructure maintenance | Recurring planned care; estimate needs review | 12 hours |
| Requested integration changes | Current requested scope, not a contractual guarantee | 18 hours |
| Total | Same weekly period and task categories | 66 hours |
| Existing usable capacity | 2 engineers × 24 hours | 48 hours |
| Uncovered work | Demand less capacity | 18 hours |
Across four weeks, that model gives 264 hours of demand against 192 hours of capacity: a 72-hour gap. It does not prove that exactly 72 hours became backlog, because priorities may change and estimates may be wrong. It does show that the plan cannot simultaneously promise all three categories within the stated capacity assumptions.
Ramon’s completed decision request reads:
Request: Review one additional individual-contributor position to cover recurring connector support and test-infrastructure work. The proposed capability is troubleshooting connectors, maintaining the relevant test fixtures, and documenting recurring fixes. It does not create a new management layer or authorize unrelated product scope.
Business need: Under the stated base assumptions, support and maintenance consume the existing 48 usable weekly hours, leaving the requested 18 hours of integration changes uncovered. Leadership must either defer that work, validate a process improvement, obtain accepted temporary capacity, or approve a longer-term staffing option. No revenue-loss amount has been established.
Proposed capacity: A fully ramped hire is modeled at 24 usable hours weekly for this work, making total capacity 72 hours. This is an assumption to review, not a promise of immediate output or interchangeable specialist coverage.
Budget scenario: For comparison only, Finance’s fictional planning envelope is $15,000 monthly in fully loaded recurring cost plus $5,000 one-time setup. Twelve unchanged months would total $185,000. This is not a salary benchmark, quote, approved budget, or current-year expense forecast. Finance must validate the components and actual start-date treatment.
Decision needed: Please select an interim work priority and authorize the appropriate workforce and financial review, or identify why another option is preferred. Position funding, requisition opening, and hiring remain separate decisions. I will update the assumptions after two more weeks of intake review.
The request is complete even though it does not fabricate approvals. It explains the work a role would cover, the gap, an illustrative cost envelope, and the decisions still required. A real submission would replace synthetic figures with authorized evidence and Finance-reviewed estimates, not present these teaching numbers as applicable to a local labor market.
Compare alternatives on the same basis
Ramon includes alternatives rather than writing a memo in which the permanent hire is the only plausible answer. Each option changes something specific in the base model:
| Option | Weekly effect under the stated assumptions | Trade-off or unverified dependency |
|---|---|---|
| Defer integration changes | Remove 18 hours of demand; 48 remain against 48 capacity | Service and maintenance fit the model, but requested integration scope waits; director must accept the priority choice |
| Simplify intake | Estimated 6-hour saving; demand falls from 66 to 60 | Still a 12-hour gap; saving unvalidated and setup itself needs an estimated 12 hours |
| Temporary specialist | Proposed 12-hour contribution less 2 hours of team coordination adds 10 net hours | Capacity becomes 58; 8-hour gap remains; availability, capability, cost, and procurement are unconfirmed |
| One permanent hire after ramp | Assumed 24 usable hours adds capacity to 72 | Six hours above base demand; recruiting, funding, onboarding, skill coverage, and ongoing demand remain uncertain |
“Defer” is an actual resource choice, not an excuse to keep every deadline while refusing resources. “Automation” needs its own implementation effort and validation. “Borrow someone” is not accepted capacity until that person’s manager and the relevant owner agree. The alternatives table should expose these conditions rather than count hypothetical help as available today.
Ramon also separates ramp from mature capacity. For a hypothetical first four weeks after a hire starts, he models 12 hours of useful contribution weekly and six hours of existing-team mentoring. The net addition is six hours, bringing effective capacity to 54 and leaving a 12-hour base gap. The exact ramp period and hours are assumptions; no candidate or start date exists.
The proposal therefore cannot rescue next week’s entire delivery plan. Even if funding is approved, the organization needs an interim priority decision while recruiting and onboarding occur. Mentoring capacity belongs in that plan, and a slow or mismatched ramp should trigger a recheck rather than pressure to report the mature estimate as already achieved.
Sensitivity: what if incoming work changes?
The second completed asset changes weekly support intake while keeping the two-hour effort estimate and the combined 30 hours of maintenance and planned integration work fixed. These are scenarios, not probability forecasts. The optional six-hour process saving remains unverified in all three rows.
| Demand scenario | Support cases weekly | Total demand before process saving | Gap against current 48 hours | Gap after hypothetical 6-hour saving | Position after a mature hire adds 24 hours |
|---|---|---|---|---|---|
| Lower | 12 | 54 hours | 6 hours | 0 hours | 18 hours of capacity above original demand |
| Base | 18 | 66 hours | 18 hours | 12 hours | 6 hours of capacity above original demand |
| Higher | 24 | 78 hours | 30 hours | 24 hours | 6-hour gap against original demand |
Under lower intake, a validated six-hour process saving would remove the modeled gap without a permanent hire. That is a reason to investigate the assumption, not bury the lower scenario. At higher intake, one mature hire alone would still leave a six-hour gap. Combining that hire with the hypothetical saving would balance the 72-hour model, but neither arithmetic balance nor a nominal surplus guarantees coverage for urgent or specialist work.
The estimate is also sensitive to case effort. At base intake, increasing the assumption from two to 2.5 hours per case adds nine hours weekly: support becomes 45 hours, total demand 75, and the current-capacity gap 27. A mature hire’s modeled 72 hours would leave three hours uncovered. Ramon therefore needs to validate case complexity as well as counts; spreadsheet precision does not validate the effort estimate.
He does not convert the hour gap into investment return. Keep the request tied to uncovered work; this example has no measured revenue effect or approved cost-benefit calculation. Hours, budget, risk, and business priorities remain related inputs rather than interchangeable units.

Record the actual decision and the next evidence needed
In the fictional review, the director accepts a two-week deferral of the integration-change work while retaining support and maintenance priorities. She authorizes Ramon to develop the workforce and Finance review, but does not approve position funding or opening a requisition. Neither a contractor nor a borrowed employee has accepted or been authorized for this work. This is a bounded interim decision, not a successful hire.
Ramon’s completed follow-up says: “For the next two weeks, the requested integration changes are deferred under the director’s decision; support and maintenance remain the priority. I will validate intake and effort assumptions and provide the updated low/base/high case. Finance review and the decision about a permanent position are pending. I will not promise a hire date or restore the deferred scope without a new priority decision.”
Keep that distinction visible when communicating with the team. If the business chooses no hire, record which work it accepts deferring or changing. If it approves review, report review rather than funding. If it approves the position, confirm the actual scope, budget, conditions, and next owners before treating downstream actions as authorized.
Adapt the request and sensitivity table, validate their assumptions, and ask the decision owner to choose the resource or scope trade-off. LandOffer.ai publishes this management guide; it does not approve headcount, provide staffing forecasts, or guarantee the return from a hire.


