Key personnel resumes and letters of commitment for federal proposals

Key personnel are the positions the government considers essential to performance: typically a Program or Project Manager, technical leads, and specialist roles named in the solicitation. Two things distinguish them from the rest of your staffing plan. First, they are evaluated: Section M usually scores their qualifications and experience. Second, they are contractual: a key personnel clause in Section H (many agencies have their own; the DoD version is common) binds you to provide the named people and to obtain the contracting officer's approval before substituting them.

The key personnel requirement is scattered by design: Section L says what to submit, Section M says how it is scored, the PWS or a Section J attachment lists the positions and minimum qualifications, and Section H carries the clause. Build one table from all four before anyone opens a resume.

1. 1

   Screen the bench against the minimums first

   Minimums are pass/fail. A brilliant candidate with nine years where ten are required is a deficiency. Screen every candidate against every minimum before anyone considers strengths.

2. 2

   Then score against the desired qualifications

   Section M often awards strengths for exceeding minimums or holding the desired qualifications. Rank the candidates who pass the minimums by how many desireds they hold and how relevant their recent work is to this agency and this PWS.

3. 3

   Confirm availability and willingness in writing

   Ask each candidate directly whether they will take the position on the proposed start date at the proposed location, and get it in writing. The letter of commitment formalizes this, but the conversation should happen before the letter is drafted.

4. 4

   Decide on contingent hires early

   If you must propose someone who is not yet your employee, check whether Section M penalizes contingent hires, whether Section L requires a letter of commitment for them, and how the person's current employer (possibly the incumbent) affects the ethics of the approach. Never propose a person without their knowledge.

A proposal resume is not the person's career resume. It is a compliance document written to one solicitation. Its job is to make each required qualification findable in seconds and provable in a sentence.

• Use the RFP's format if one is given, field for field, in its order. If none is given, use a one-page qualifications table on top (requirement, how met, where in resume) followed by the narrative.
• State the qualification in the requirement's words. If the PWS says "10 years of experience managing IT service contracts", the resume says "11 years managing IT service contracts (2015 to present)" near the top.
• Give dates that let years be computed. Month and year for every position. Evaluators add them up; unclear dates get counted conservatively.
• Name the certification and its status. "PMP, Project Management Institute, active, certification number available on request." Expired certifications do not count.
• Lead each position with relevance to this PWS. A paragraph on a comparable contract with size, scope and results beats a list of duties.
• Cover clearances precisely. Level, investigation type and date where allowed, and whether it is active or current.
• Respect the page limit and the font instructions. Resumes over the limit are cut at the limit, often losing the very page with the certification.

A letter of commitment is a signed statement from the proposed individual that they will accept the position if the contract is awarded. Solicitations usually require one for every proposed key person who is not a current employee, and some require it for all key personnel. Even when optional, it is worth including: it answers the evaluator's quiet question about whether the person is real and available.

The key personnel clause outlives the proposal. Typical terms: the contractor shall provide the named individuals; substitutions require advance written notice (often 15 to 30 days) and the contracting officer's approval; replacements must have qualifications equal to or better than the original; and some clauses forbid substitution for a period after award except for reasons beyond your control. Read the clause before you propose, because it defines the promise you are making.

• Keep the requirement table, the resumes and the letters in the contract file; substitution requests must show the replacement meets the same minimums.
• Brief proposed personnel on the clause so they understand the commitment period.
• If a proposed person becomes unavailable between submission and award, notify the contracting officer promptly and propose a qualified replacement. Silence is the worst option.

How ProposalWorkspace handles this

Key personnel from bench to submission-ready package

ProposalWorkspace extracts the RFP's required positions with their minimum qualifications, ranks your bench against them with evidence from each person's current resume, reviews a resume against the job description line by line, generates recruiter-ready job descriptions and letter of commitment formats, and checks a signed letter against the RFP's mandatory statements before it ships.

Start free trialSee it in detail

This guide is general information for federal contractors drawn from the FAR and standard capture and proposal practice. It is not legal advice; always read the specific solicitation and consult counsel on protests, contract terms and compliance questions.