Staffing a federal research task order

The evaluator is asking one question

Strip away the format requirements and every staffing section on a research task order is answering one question: will these people actually do this work, starting on the first day of the period of performance? The evaluator cannot interview anyone. They have a staffing plan, a table of hours, some résumés and perhaps a few letters. From those pages they form a judgment about whether the team is real, whether it fits the work, and whether it will still be there in month nine. Everything in the staffing volume should be built to make that judgment easy and favorable.

Research task orders, the analysis, evaluation and study work agencies buy for health, transportation, economics and program evaluation, have a fairly stable shape. The roles repeat, the hours follow a recognizable pattern, and evaluators have seen enough of them to notice when a plan does not add up. That stability helps you: once you know the shape an evaluator expects, you can show them the plan fits it.

The roles on a typical analysis task order

Titles vary by agency and vehicle, but most research and analysis work is carried by some version of the roles below. A given task order may combine two of them in one person or split one across two people. What matters is that every function is covered and that each person's role is unambiguous.

Role	Typical responsibilities	What the evaluator looks for
Principal investigator	Owns the research design and the conclusions; signs off on methods; leads briefings to the agency	Directly relevant prior work, publications or reports on similar questions, enough hours to actually lead
Postdoctoral researcher or senior analyst	Runs the analysis day to day; builds models; drafts technical sections; supervises analysts	Methods experience matching the work, software fluency, evidence of independent analysis
Health economist or domain specialist	Brings the subject knowledge: cost-effectiveness methods, transportation safety, program rules	Specific expertise the requirement names, credentials where the field expects them
Research analyst	Data cleaning, coding, literature review, tables and figures, quality checks	Relevant degree, tools named in the requirement, a realistic number of them
Project manager	Schedule, deliverables, monthly reporting, invoicing, the government relationship	Federal reporting experience, clear authority, a named point of contact

Two roles get missed. The first is someone who owns data management, whether a data manager or the senior analyst explicitly assigned the job, because data agreements, secure storage and documentation take real hours. The second is editorial and quality review. Research reports are read by people outside the field, and a final pass for clarity, consistency and Section 508 accessibility should be somebody's assigned work, not an afterthought on the last weekend.

How the hours mix across roles

The hours table is where an evaluator tests whether the plan is serious. They look at two things: whether the total effort fits the scope, and whether the distribution across roles fits how research actually gets done. The second test catches more proposals than the first.

Read the shape rather than the numbers. Most of the hours sit with the people who do the analysis. The principal investigator carries a real share, enough to design the study, review the work and stand behind the conclusions, but not so much that the plan looks like one expensive person doing everything. The project manager's share is modest and steady across the period of performance.

The patterns that worry evaluators are recognizable. A principal investigator at a token fraction of time reads as a name borrowed for the proposal. A plan where senior people carry most of the hours reads as either overpriced or unrealistic, because senior people rarely clean data. A domain specialist named for expertise the requirement emphasizes but given a few dozen hours reads as decoration. Spread hours over time as well as roles: the hours table should show analysts front-loaded during data work, the principal investigator heavier at design and at the final report, and the project manager level throughout.

Labor categories are the contract's vocabulary

On most task orders, people are priced and billed by labor category, not by name. A labor category is a defined role with a description and minimum qualifications, usually a degree level and years of relevant experience. The vehicle or the solicitation sets the categories. Your job is to map each proposed person to a category they genuinely qualify for.

Read the category definitions closely. If the solicitation says a senior research analyst needs a master's degree and a stated number of years of experience, the evaluator will check the résumé against both. Some vehicles allow experience to substitute for education on a stated ratio. Use the substitution only where the vehicle permits it, and say on the résumé that it applies.

Keep the mapping consistent across volumes. The person the technical volume calls the lead analyst should appear under the same labor category in the price volume, at hours that match the role described in the staffing plan. Evaluators cross-check, and a mismatch between volumes is one of the easiest ways to lose credibility.

How rates are structured

Rates are proposed per labor category, per year of performance. On a time-and-materials or labor-hour order they are typically fully burdened, meaning the hourly rate includes salary, fringe benefits, overhead, general and administrative costs and profit. On a vehicle with ceiling rates, the rate you propose on an order is usually at or below the ceiling for that category, and competition on an order often pushes proposed rates below the ceiling.

Most multi-year orders include escalation from one year to the next. State the escalation assumption and apply it consistently. The price narrative should also explain how the hours were estimated, tying them to the work breakdown: so many hours for the literature review, so many for each analysis, so many for each report. Price evaluators look for that link. A total that is plausible but unexplained is weaker than a total built visibly from the tasks.

What evaluators check in qualifications

Evaluators read résumés against the solicitation, not against each other. They are checking a short list of things, and résumés that make the list easy to check score better.

• Category minimums. Degree, field and years of experience for the labor category the person is proposed under.
• Relevance. Prior work on questions like this one: the same population, method, data source or policy area.
• Recency. Whether the relevant experience is current or a decade old.
• Named methods and tools. The statistical methods, models, software and datasets the requirement names, shown in actual work.
• Role fit. Evidence the person has done this role before, such as leading a study, not only contributing to one.
• Availability. A clear statement of the person's commitment to this work and when they can start.

Write each résumé for the requirement. A generic résumé that lists every project a person has touched makes the evaluator hunt. A tailored one leads with the three or four pieces of work most like this task, says what the person did on each in a sentence, and puts the degree and years where the category check is quick.

Key personnel and commitment letters

Many research task orders designate certain roles as key personnel, usually the principal investigator and sometimes the project manager or a lead specialist. Key personnel are named in the proposal, evaluated individually, and bound by the contract's key personnel clause, which typically restricts substitution after award without the contracting officer's approval of a replacement with equal or better qualifications.

A commitment letter is the strongest evidence that a named person will show up. It should be signed by the person, state the role and the level of effort, confirm they are available for the period of performance, and confirm they have reviewed how they are described in the proposal. When the person is not your employee today, the letter matters even more, and evaluators read it closely. Many solicitations require such letters for key personnel; include them for other critical roles as well when the solicitation allows.

Do not name anyone who has not agreed to be named. Beyond the integrity problem, a person who learns they were proposed without consent is unlikely to accept the role at award, and the substitution request that follows will be the first thing the contracting officer remembers about you.

Consultants and part-time specialists

Research orders often need deep expertise for a narrow slice of the work: a clinician to review a care pathway, a survey methodologist to vet a sampling frame, an economist to check a discounting assumption. Bringing that person in as a consultant at a limited number of hours is normal and evaluators accept it, provided the plan is specific.

Say exactly what the consultant does and when: which tasks, which deliverables, how many hours in which months. Price them under the category the solicitation provides for specialists or as a consultant cost, as the solicitation directs. Get the same signed commitment you would get from a key person, and make sure the consultant's availability lines up with the months their work is scheduled. A specialist whose hours fall in a month they have already committed elsewhere is a gap, not a strength.

Continuity: the month-nine question

Research staff move. Postdoctoral researchers take faculty jobs, analysts change employers, specialists get pulled onto other work. Evaluators know this and want to see that the plan survives it. A continuity section answers how the work keeps going when a person leaves.

Name a backup for each key role, or at least describe the bench the replacement would come from. Describe how knowledge is held in the work rather than in one person's head: documented code, shared analysis files, a methods log, overlapping assignments so two people know each dataset. State the substitution process and how quickly a replacement would be proposed. Keep it specific. "We maintain a deep bench" convinces nobody. "The senior analyst and a second analyst both work the claims data, so either can carry the analysis" is believable.

Presenting a team that exists on day one

The best staffing sections read like a description of a working team, not a list of qualified individuals. An evaluator is not scoring résumés. They are scoring their confidence that this specific group of people will be doing this specific work in month one and month nine. That means showing how the people relate to each other and to the work.

Show the structure. A one-page organization chart with names, roles, labor categories and reporting lines lets the evaluator see the team at a glance. Map people to tasks: a simple matrix of tasks against people, with hours, shows who does what and confirms the hours table is real. Show that the people have worked together, if they have, on what and when. Show the first thirty days: who starts on day one, what each person does in the first month, and when the first deliverable lands. A plan that describes week one concretely is a plan an evaluator believes.

Match the language of the evaluation criteria. If the solicitation scores "qualifications of key personnel" and "adequacy of the staffing approach" separately, give each its own heading and answer it directly. Evaluators work from a scoring sheet, and making their job easy shows up in the score.

A staffing plan checklist

• Every function covered: design, analysis, domain expertise, data management, quality review, project management.
• Each person mapped to a labor category whose minimums their résumé visibly meets.
• Hours by role and by period that follow the shape of the work and tie to the task breakdown.
• The same names, roles, categories and hours in the technical and price volumes.
• Résumés tailored to the requirement, most relevant work first, in the required format.
• Signed commitment letters for key personnel and other critical roles.
• Consent from every named person to be proposed at the stated level of effort.
• A continuity plan with backups or a named bench and the substitution process.
• An organization chart and task matrix on one page each.
• A day-one plan showing who starts and what they do in the first month.

Where staffing plans lose points

• A token principal investigator. A famous name at a sliver of effort reads as borrowed.
• Hours that do not match the narrative. A technical volume that describes extensive fieldwork with no hours for it.
• Résumés that miss the category minimum. The evaluator checks, and a miss can make the person unacceptable for that category.
• To-be-determined in critical roles. Sometimes unavoidable for junior roles; rarely acceptable for anyone the evaluation names.
• No continuity story. A plan that assumes nobody will leave over a multi-year order is not a plan.
• Inconsistency across volumes. Different hours or categories for the same person in two places.

Frequently asked questions