The technical and management approach (often called the technical volume) is the part of your RFP response that explains exactly how you will do the work and how you will manage it. In most best-value procurements it carries the most weight, and it is where evaluators record the strengths and weaknesses that decide the award. This chapter shows how to write a technical approach that answers the scope of work requirement by requirement, and covers methodology, the work plan, staffing and key personnel, quality control, risk, transition, graphics, strong vs weak paragraphs and a reusable section skeleton.
Start from your compliance matrix and annotated outline (Proposal Structure and Compliance). If you have not yet broken the solicitation into individual requirements, do that first with How to Read and Shred an RFP. Fill-in plans are in Technical and Management Plan Templates.
What do evaluators look for in a technical approach?
Evaluators ask three questions of every section: does this offeror understand what we need, is the approach specific and credible, and how risky is it? They record strengths, weaknesses and deficiencies. A single deficiency can sink an otherwise good proposal, so compliance comes first and persuasion second.
| Award method | How the technical part is judged | How to write it |
|---|---|---|
| Low-bid IFB (sealed bidding) | Not scored; the bid must conform to the specifications and the lowest responsive, responsible bidder wins | Usually no narrative. Complete forms and submittals exactly, with no conditions or exceptions |
| Lowest price technically acceptable (LPTA) | Pass or fail against stated minimums; extra quality earns no credit | Prove each requirement is met, clearly and briefly. Don't gold-plate: extras raise price, not rating |
| Best-value tradeoff | Rated against the evaluation factors; strengths can justify a higher price | Answer every requirement and build in strengths: specific methods, measurable benefits, lower risk |
| State and local RFPs scored on points | Criteria and points listed in the RFP, such as approach, experience, staffing and cost | Use the criteria as headings, give the highest-point criteria the most space, answer every question |
- Statement of work (SOW)
The part of the solicitation describing the work, often in detail and sometimes including how to do it.
- Performance work statement (PWS)
A scope written as outcomes and measurable standards. You propose the method; the agency judges results.
- Statement of objectives (SOO)
A short list of goals. You define the tasks yourself, often by writing your own work statement.
- Strength, weakness, deficiency
Evaluator findings: an advantage to the agency, a flaw that raises the risk of failure, or a failure to meet a requirement.
- Key personnel
Named people the solicitation treats as essential, usually with minimum qualifications, resumes and sometimes signed commitment letters.
- Quality control plan (QCP)
Your plan for checking your own work. The agency's plan for checking you, common in performance-based contracts, is the quality assurance surveillance plan (QASP).
How to write a technical approach requirement by requirement
The surest way to lose points is to make an evaluator hunt. Evaluators work from a checklist built from the solicitation, so follow the order and numbering of the instructions and the scope of work, and answer every “shall” and “must” where they expect it.
Step 1: Cite the requirement
Open each subsection with the reference and the agency's own words, for example “PWS 3.2.1 Help Desk Support.” The evaluator knows exactly which checklist line you are answering.
Step 2: Show you understand it
In a sentence or two, explain what the requirement is for and what makes it hard here: peak volumes, aging equipment, many sites, regulatory deadlines. Add insight; do not paraphrase it back.
Step 3: Explain how
Describe the method step by step, naming the tools, standards and procedures. “Tickets are triaged within 15 minutes using a three-level priority matrix” beats “we use industry best practices.”
Step 4: Say who and when
Name the responsible role or person, the labor categories and the schedule or frequency. Tie deliverables to the solicitation's due dates.
Step 5: State the benefit and the proof
Close with what the agency gains and evidence that it works: a result on a similar contract, a metric, a certification. This is the sentence that becomes a strength.
Tip: Write the benefit so an evaluator could paste it into the evaluation report almost word for word.
| Reference | Requirement (short form) | Where answered | Proof or win theme | Owner |
|---|---|---|---|---|
| PWS 3.2.1 | Respond to priority 1 tickets within 30 minutes, 24/7 | Vol. I, 2.3.1, p. 7; Figure 4 | No missed priority 1 windows in 18 months on current county contract | J. Rivera |
| Section L.4.2(b) | Describe transition from the incumbent | Vol. I, 3.6, pp. 18–19 | 45-day transition with parallel operations | M. Chen |
Describe a methodology, not a promise
Your methodology is the “how” behind the whole job: the phases, processes and tools that tie individual requirements together. Evaluators want a logical approach that fits this customer, not a process diagram pasted from your last bid.
- Name it and explain it. If you use a recognized framework or standard, say which one and how you apply it here.
- Show the phases: planning, startup, steady-state operations and continuous improvement, and what triggers each move.
- Connect it to the customer: their sites, volumes, users, regulations or legacy systems.
- Answer what, how, who, when and why for every major element. Evaluators notice the missing one.
Work plan and schedule
A work plan shows you have thought the job through from day one. Break the work into tasks that match the scope numbering, show dependencies and milestones, and tie each deliverable to the solicitation's dates. Larger efforts call for a work breakdown structure and a Gantt chart; for a small municipal contract, a table of tasks, owners and dates is enough.
Weeks 1–2
Kickoff and planning
Kickoff with the agency, confirm priorities, finalize the project management and quality control plans.
Weeks 3–6
Setup and pilot
Install scanning stations, scan a 5,000-page pilot batch; the agency reviews image quality and indexing.
Months 2–10
Production
Scan and index by priority, with weekly progress reports and monthly quality audits.
Month 11
Acceptance
Agency tests a random sample; rejected batches are reworked.
Month 12
Closeout
Deliver final indexes, return originals, hand over documentation and lessons learned.
Keep the schedule realistic and consistent. Evaluators compare it with your staffing and price: a schedule that needs four people for a job priced for two is a weakness or worse (see basis of estimate in the pricing chapter).
Staffing plan and key personnel
The staffing plan answers “who will actually do this, and are there enough of them?” Show an organization chart with names for key roles, how your team works with agency staff, where subcontractors fit and who can make decisions. A staffing matrix mapping roles to tasks makes it easy to check; there is a fill-in staffing plan template.
| Role | Name | FTE | SOW tasks | Key person? |
|---|---|---|---|---|
| Project manager | Dana Ortiz, PMP | 1.0 | 1.0 Management, 5.0 Reporting | Yes |
| Senior systems engineer | Raj Patel | 1.0 | 2.0 Operations, 4.0 Security | Yes |
| Help desk technicians | Recruiting from incumbent staff where possible | 4.0 | 3.0 Help desk | No |
| Quality control manager | Lena Brooks | 0.25 | 6.0 Quality | No |
For each key person, map education, certifications and experience directly to the solicitation's minimum qualifications, in the required resume format, and show where their experience matches this work. A ready format is the key personnel resume template.
Round out the management approach with how you will communicate: the status reports you will deliver and how often, regular meetings with the agency's contract manager, how scope or schedule changes are requested and approved, and the escalation path from a day-to-day issue to a company executive.
Quality control plan
Your quality section explains how you will catch problems before the customer does. In performance-based contracts the agency checks your work against its own surveillance plan, so make your controls cover the same standards. Cover five things (or start from the quality control plan template):
- Standards: what “good” means for each deliverable, using the solicitation's acceptance criteria.
- Inspections: who checks what, how often and how, such as a weekly sample of completed work.
- Independence: the checker is not the doer, ideally reporting outside the project line.
- Corrective action: how you find root causes, fix them and confirm the fix, with time frames.
- Reporting: the metrics you report to the agency, and how often.
“Our quality control manager, who reports to our operations director rather than the project manager, inspects a random 10% of completed work orders each week against the PWS acceptance criteria. Any defect opens a corrective action record within 24 hours; the project manager identifies the root cause and fix within five business days, and the quality control manager verifies it. The monthly status report shows first-time acceptance rate, open corrective actions and trends.”
Risk management
Evaluators know things go wrong; they want proof you have identified this contract's specific risks and planned for them. Generic risks (“staff turnover”) earn little. Specific risks with a mitigation and an owner earn credibility, and in a best-value evaluation a strong mitigation can become a strength. A blank risk register template is in the templates handbook.
| Risk | Likelihood | Impact | Mitigation | Owner |
|---|---|---|---|---|
| Incumbent staff decline offers, slowing transition | Medium | High | Early outreach with competitive offers; two trained backups per role from our bench | Project manager |
| Records arrive in worse condition than sampled | Medium | Medium | Pilot batch recalibrates throughput; weekly forecast to the agency | Operations lead |
| Winter storm closes sites at peak season | Low | High | Remote plan for office tasks; on-call crew with four-wheel-drive vehicles | Field supervisor |
Transition plan
If someone else does the work today, the agency's biggest fear is a service gap at changeover. A transition-in (phase-in) plan shows how you will take over without disruption. Many service contracts also ask for a phase-out plan for handing the work to a successor at the end. See the transition-in plan template.
- Stage 1: Award to kickoff
Mobilize the transition team; agree the schedule with the agency
- Stage 2: Knowledge transfer
Interview incumbent staff, review documentation, shadow operations
- Stage 3: Staffing and setup
Hire or retain staff; set up accounts, tools, badges and space
- Stage 4: Parallel operations
Work alongside the incumbent where allowed, with readiness checks
- Stage 5: Full responsibility
Assume all work on an agreed date; report daily at first
Graphics and action captions
Graphics let skimmers grasp a process, organization or schedule at a glance. Good candidates are process flows, organization charts, schedules, maps of sites and coverage, and before-and-after comparisons. Number each one, refer to it in the text and keep it readable at the font sizes the solicitation allows. Layout, headings and white space are covered in readability and graphics.
Action caption: states the benefit
- Do: Figure 3. Topic-based routing sends rent and repair calls straight to trained specialists, cutting resident hold times.
- Do: Figure 5. Two crews based within 20 minutes of every school reach emergency calls inside the two-hour window.
- Do: Figure 7. Parallel operations in weeks 4–6 keep every service running while our team takes over.
Label only
- Don't: Figure 3. Call flow.
- Don't: Figure 5. Map of crew locations.
- Don't: Figure 7. Transition schedule.
Strong vs weak technical paragraphs
One requirement, answered two ways: “The contractor shall provide snow and ice removal at all 12 District facilities, with parking lots and walkways cleared before 6:30 a.m. on school days.”
“Our company has extensive experience in snow removal and will provide snow and ice removal at all District facilities in accordance with the requirements of the RFP. We have a dedicated team and modern equipment, and we are committed to safety and customer satisfaction.”
Why it is weak: it restates the requirement, gives no method, names no people or equipment, ignores the 6:30 a.m. deadline and offers no proof.
“PWS 4.3 Snow and Ice Removal. We will clear all 12 facilities before 6:30 a.m. on school days using three plow routes of four sites each, sequenced so the two high schools with early buses are finished first (Figure 6). Crews deploy at 2:00 a.m. whenever 2 inches or more is forecast; a separate hand crew clears and treats walkways with a concrete-safe de-icer. Field supervisor Tom Walsh confirms each site is clear by text to the facilities director by 6:15 a.m. Last winter, using the same routing for a neighboring district, we met the opening deadline on all 31 storm days.”
Why it is strong: it cites the requirement, gives a specific method, names the accountable person, commits to the deadline with a verification step and proves it with a comparable result.
A technical approach section skeleton you can reuse
Use this skeleton for each major requirement or evaluation factor. It enforces the order evaluators expect and keeps writers out of boilerplate. Swap in the solicitation's own headings and numbering.
Template
Technical approach section skeleton (one requirement)
One subsection per requirement or evaluation factor, in the order evaluators read. Matching management, staffing, quality control, transition and risk templates are in Technical Approach and Management Plan Templates.
When to use it
Best-value and points-based RFPs. For LPTA bids, keep Understanding, Our approach and Who and when, and trim the rest to stay brief.
[SOLICITATION REFERENCE] [REQUIREMENT HEADING IN THE AGENCY'S WORDS] Understanding [ONE OR TWO SENTENCES ON WHAT THIS REQUIREMENT IS FOR AND WHAT MAKES IT DIFFICULT FOR THIS AGENCY] Our approach 1. [STEP 1: ACTION, TOOL OR STANDARD] 2. [STEP 2] 3. [STEP 3] See Figure [NUMBER]: [ACTION CAPTION STATING THE BENEFIT]. Who and when [ROLE OR KEY PERSON] is responsible, supported by [LABOR CATEGORIES]. [FREQUENCY, MILESTONES OR DELIVERABLE DATES FROM THE SOLICITATION]. Quality and risk We will measure [METRIC] against [STANDARD]. If [RISK] occurs, we will [MITIGATION]. Benefit to [AGENCY NAME] [MEASURABLE BENEFIT TIED TO A HOT BUTTON OR EVALUATION FACTOR] Proof On [COMPARABLE CONTRACT], [RESULT WITH A NUMBER]. See [REFERENCE OR SECTION].
Fields to fill in
- [SOLICITATION REFERENCE]
- The exact paragraph number, such as PWS 3.2.1 or Section L.4.2(b), matching your compliance matrix.
- [STEP 1–3]
- Concrete actions naming tools, standards or procedures; add steps as needed.
- [ACTION CAPTION STATING THE BENEFIT]
- A full sentence saying what the graphic shows and why it matters to the agency.
- [METRIC / STANDARD]
- Use the solicitation's performance standards or acceptance criteria where they exist.
- [COMPARABLE CONTRACT]
- A project from your past performance section; only results you can document.
Frequently asked questions
What is the difference between a technical approach and a management approach?
The technical approach explains how you will do the work: methods, tools and processes for each requirement. The management approach explains how you will run the contract: organization, key personnel, staffing, schedule, communication, quality control, risk and transition. Some solicitations combine them in one volume; others score them as separate factors.
How detailed should a technical approach be?
Detailed enough that an evaluator can see exactly how each requirement will be met, by whom and when, and within the page limit. Specific beats long: name methods, tools, standards and metrics instead of adding adjectives. Give the most space to the most heavily weighted factors.
Should I copy the language of the statement of work?
Use the solicitation's terms and headings so evaluators can find your answers, but do not simply restate requirements. Every subsection should add your understanding, your method, the people responsible and proof. Copying the requirement back earns no strengths.
What if I have not identified all my key personnel yet?
Check the solicitation first: if it requires named key personnel with resumes or commitment letters, you must provide them. If it allows it, describe the qualifications and your recruiting plan for unfilled roles, and label contingent hires honestly. Never name someone who has not agreed to be proposed.
What should a quality control plan include in a proposal?
Performance standards for each deliverable, inspection methods and frequency, who performs inspections and their independence from production, how defects are corrected and verified, and the metrics you will report to the agency.
What is a transition plan in a proposal?
A transition-in (phase-in) plan shows how you will take over work from the current contractor or start a new service without disruption: knowledge transfer, hiring, setup, any period of parallel operations and the date you assume full responsibility. Some solicitations also require a phase-out plan for handing the work to a successor at the end of the contract.
How do I write a technical approach for an LPTA solicitation?
Prove that you meet every minimum requirement clearly and briefly, following the instructions exactly. Extra features earn no credit and may raise your price, so focus on compliance, completeness and low risk. Then compete on price.
Complete handbook
Download the complete handbook (PDF)
All 8 chapters, templates and checklists, ready to print or share.
Put it into practice
Search open RFPs from federal, state, local, education, private and non-profit issuers, each with the RFP Detector Score.
Find RFPs