The question every evaluation should ask
Every proposal for technical work promises experienced people. The résumés are strong, the oral presentation is sharp, and the person who answers the hard question in the room clearly knows the subject. Then the contract starts, and the people on the weekly call are not the people from the presentation. The question that decides most services outcomes is not which firm has the best methodology. It is who, by name, will do the work, and for how many hours.
This is not a story about bad actors. It is a structural feature of how much of the services market staffs work, and it can be managed. Evaluators can ask for evidence that predicts who will show up. Contracting officers can write requirements that make the answer binding. CORs can check, in the first month, whether what was proposed is what arrived.
This guide covers the difference between senior-led and pyramid staffing, what senior-led delivery changes for the program office, how to verify it during an evaluation, and what to watch after award.
The people in the proposal and the people on the project
Proposal teams are built to win. They put forward the most credentialed people a firm can name, because that is what scores. After award, those people are often committed elsewhere. They were on the proposal because they were impressive, not because they were available. The firm then staffs the work with whoever is free, frequently more junior, with the senior names attending a kickoff and a quarterly review.
The pattern has a recognizable sequence. A named lead attends the kickoff and the first two meetings. A "day-to-day lead" appears, introduced as someone who will handle the details. Drafts arrive written by people the program office has never met. Questions take a week because the answer has to travel up and back down. By month three, the person whose résumé carried the technical score is a name on the status report and nowhere else.
None of that necessarily breaches the contract. Unless the requirement designated key personnel and required named people to perform a stated share of the work, a firm can usually meet its obligations with a different team. The protection has to be built in before award.
Two staffing models, side by side
Most technical services are staffed in one of two shapes. In a pyramid, a few senior people sell and oversee, a middle layer manages, and a broad base of junior staff does most of the hours. In a senior-led model, the experienced people who scoped the work lead it and do a large share of it themselves, with specialists brought in for specific pieces.
| Dimension | Senior-led | Pyramid |
|---|---|---|
| Who scoped the work | The same person who leads and performs it | A senior seller or capture lead who hands it to a delivery team |
| Who the COR talks to | The person making the technical decisions | A project manager who relays questions to the people doing the work |
| Where the hours go | Mostly to experienced people, concentrated on judgment-heavy tasks | Mostly to junior staff, with senior hours in review and oversight |
| Speed of an answer | Often the same day, because the person asked is the person who knows | Depends on how many layers the question passes through |
| Handoffs | Few; context stays with the people who built it | Several; context is summarized at each layer |
| Where it fits best | Analysis, design, research, technical review and novel builds where judgment drives the result | Large, repeatable volume work with stable procedures |
Neither model is wrong in itself. A help desk, a records conversion project or a large data-entry effort can run well on a pyramid, because the work is defined and the procedures carry the quality. The problem arises when judgment-heavy work, the kind where one decision about method or design determines the value of everything that follows, is staffed as if it were volume work.
Watch the blended rate as well. A pyramid often shows a lower average hourly rate, which reads well on a price evaluation. On judgment-heavy work it can also need more total hours, because junior staff take longer on unfamiliar problems and senior review hours are added on top. Compare total price for the outcome, not the average rate per hour.
What senior-led means in practice
Senior-led does not mean only senior people. It means the person who understood the problem well enough to scope and price it stays on the work, leads it, and performs the parts that need the most judgment. Specialists join for specific tasks, and junior staff can do well-defined pieces under close direction. The center of gravity stays with the person who knows why each decision was made.
Three things follow. The design decisions in week two are made by someone with the experience to make them, rather than by someone who will learn from getting them wrong. The person who wrote the method section in the proposal is the one who has to make it work, which keeps the proposal honest. And when the program office's understanding of the problem shifts, as it usually does by month two, the person who hears it can change the approach without a round of internal meetings.
A direct line to the people who decide
For a COR, the daily cost of a layered team is time. A question about a data definition goes to the contractor's project manager, who forwards it to an analyst, who asks a technical lead, who replies with a question, which goes back down the chain. A two-minute answer takes four days, and the answer that arrives has been summarized twice.
On a senior-led team, the COR's question goes to the person who is doing the analysis and who has the authority to decide how it is done. That person can say yes, no, or "here is the tradeoff" on the spot. Program staff get better answers too, because they are talking with someone who has seen the same problem in other settings and can tell them which of their options is likely to work.
The direct line also runs the other way. A senior lead who spots a risk, such as a dataset that does not support the planned analysis or a requirement that conflicts with a policy, raises it directly with the COR the week it appears. In a layered team, the same risk is often softened at each level before it reaches the government.
Faster answers, fewer handoffs
Every handoff loses something. When one person scopes the work, another plans it, a third does it and a fourth reviews it, each transition drops a little of the reasoning. The reviewer checks the work against the plan, not against the problem. The analyst follows the plan without knowing which assumptions were fragile. The result is work that matches the documentation and misses the point.
Every handoff loses something, and on judgment-heavy work the thing it loses is usually the reason a decision was made. Senior-led delivery does not eliminate handoffs, but it keeps the critical ones inside one head. The person who chose the method also checks whether the results make sense, and notices when they do not.
What Best Predicts the Proposed Team Shows Up
Relative weight of each kind of evidence, in our judgment. Illustrative, not measured data.
How to verify it during an evaluation
Evaluators cannot see the future team, but they can ask for evidence that binds it. The strongest evidence ties names to hours and hours to price, because that is what a firm has to deliver against.
Named people for the roles that matter. Ask offerors to name the people who will fill the lead and senior technical roles, not just describe the labor categories. A role description with "or equivalent" attached tells you what the firm hopes to staff, not whom.
Hours assigned to named people. Ask for a staffing matrix that shows each named person's hours by task or phase. If the lead's name appears on forty hours of a two-thousand-hour effort, you know who is doing the work. If the matrix shows "TBD" in most rows, you know that too.
Signed commitments. Ask for a signed statement from each named person confirming availability for the stated hours and period. A signature changes what a firm is willing to promise, because it involves the person, not just the proposal team.
Live answers from the people named. If the evaluation includes oral presentations or a technical interview, require that the named lead present and answer questions, and that the people presenting be those who will perform. The quality of unscripted answers is hard to fake.
A checklist for evaluators
Use these questions when reading staffing plans and technical approaches. They work for best-value tradeoffs and for technical acceptability reviews alike.
- Are the lead and senior technical roles filled by named people, not labor category descriptions?
- Does the staffing matrix assign hours to each named person, by task or phase?
- Do the hours for the named lead reflect leading and doing the work, not only oversight?
- Has each named person signed a commitment to the stated hours and period?
- Did the person who will lead the work write or present the technical approach?
- Do the résumés describe specific recent work similar to this requirement, with the person's own role stated?
- Is the price consistent with the staffing, so the senior hours shown are actually paid for?
- Does the proposal explain who the COR will talk to day to day, and is that person on the matrix?
The price check deserves emphasis. A proposal that shows senior people on most of the hours and a price that only works with junior rates has told you, in arithmetic, which of its two claims to believe.
Writing it into the requirement
Verification during evaluation only matters if the result binds after award. That takes contract language, written by the contracting officer, before the solicitation goes out.
Make the proposed team the contracted team
Designate the lead and senior technical roles as key personnel. Require that proposed key personnel perform a stated minimum share of the hours on their tasks, and that substitutions be requested in writing with a résumé of equal or better qualifications and approved by the contracting officer before the change. Ask for the staffing matrix to be incorporated into the contract or the approved project plan. Require monthly reporting of hours by named person, which also gives the COR the data to see drift early.
Keep the burden proportionate. A short order for a defined analysis needs one or two named people and a simple commitment, not a full key personnel regime. A multi-year program with complex technical work justifies more. The test is whether the language protects the specific judgment the work depends on.
What to watch after award
The first ninety days show whether the proposed team is the actual team. Look for a few concrete signals.
Who attends the kickoff and the first working sessions. The named lead should be there and should run the technical discussion. If they introduce someone else as the person to call, ask what the named lead's role will be week to week.
Who writes the deliverables. The first draft deliverable should read like the person you met. Ask the lead to walk through it live. Someone who wrote it, or directed every decision in it, can explain each choice without notes.
Hours by name. Compare monthly hours by named person against the staffing matrix. A lead whose hours have fallen to a tenth of plan in month two is a conversation to have in month two.
Substitution requests. Early substitutions are sometimes legitimate; people change jobs and have family emergencies. A substitution in the first sixty days for a person who signed a commitment is worth a careful look at the replacement's qualifications and a direct conversation with the firm.
Who answers when something goes wrong. The first real problem on a contract, a missed data delivery or a result that does not hold up, shows the actual structure. If the named lead calls the COR the same day with a plan, the model is working. If the explanation comes from someone new, through a formal letter, a week later, it is not.
What good looks like six months in
On a well-run senior-led engagement, the COR knows who to call for any question and gets a useful answer quickly. Status reports describe decisions, not just activities. Risks arrive early, with a recommendation attached. Program staff say the contractor understands their problem, and they mean the person, not the firm.
Above all, the work that comes back reflects judgment the program office did not have to supply. That is the value of experienced people doing the work: they see the problem the requirement was written to solve, not only the requirement.
Frequently asked questions
A staffing model in which the experienced people who scoped the work lead it and perform the judgment-heavy parts themselves, with specialists for specific tasks. It contrasts with a pyramid model, where senior people sell and oversee while most hours go to junior staff.
Ask for named people in the lead roles, a staffing matrix with hours by named person, signed availability commitments, and live presentations by the people who will perform. Then check that the price supports the senior hours shown.
No. For large, repeatable work with stable procedures, a pyramid can be efficient and appropriate. The risk is staffing judgment-heavy work, such as analysis, design, research or technical review, as if it were volume work.
A key personnel clause that requires written substitution requests, replacements with equal or better qualifications and contracting officer approval before any change. Monthly hours by named person let the COR see drift before it becomes a problem.