Back
No items found.

How to write a consulting services RFP

Erfan Pirhooshiar
Erfan is the Marketing Manager for Flowcase, creating content for proposal teams

Picture a scoring panel with five responses to a consulting services RFP (request for proposal), where the proposed team carries a large share of the score. One firm sent 30 resumes in three layouts. Another named a partner as engagement lead with no time allocation. No two firms described their past projects with the same fields, so "similar experience" meant a six-week review in one proposal and a three-year program in the next. The panel cannot compare the people who would do the work, so the discussion drifts to price and the lowest fee wins by default. By the end of this guide, you will be able to write the RFP section by section so the proposals come back comparable, including the team and experience requirements most RFPs leave vague.

Most consulting RFPs spend pages on company background and one line on the team, usually some version of "provide CVs of key staff." The people are what you are buying. Write the team requirements as carefully as the scope, and write the whole RFP knowing a bid manager will turn every sentence into a task list.

Before you start: confirm an RFP is the right route

To write an RFP for consulting services, describe the business problem and the decision the work must inform, then define the scope, deliverables and acceptance criteria. Specify the named team and project experience you expect, and set the submission format, pricing model, budget range, timeline and Q&A rules. Publish the evaluation criteria with their weights, and attach your legal terms.

Pick the route that matches what you need back from the market:

  • An RFP when you need firms to propose an approach, a team and a price you can compare.
  • An RFI (request for information) when you want to scan the market without committing to buy.
  • An RFQ (request for qualifications) when you select on credentials, as many AEC (architecture, engineering and construction) and public-sector buyers do. The same acronym can mean request for quotation, which fits a defined commodity where only price matters.
  • A direct award for small, urgent or follow-on work, where your rules allow it.

If you are unsure whether you need a full proposal or a price-only response, settle the difference between a bid and a proposal first. AEC and public-sector readers should also read the note on qualifications-based selection in the team step.

Have these ready before you draft: a sponsor who owns the decision, a project lead, named contacts in procurement, legal and finance, the panel who will score, an approved budget range, a target decision date and a short list of firms to invite.

Describe the problem and the decision it feeds

Introduce your organization in two short paragraphs, not ten. Then describe the business problem and name the decision the engagement must inform. For example, instead of "ERP strategy," write "decide whether to consolidate three regional finance systems before the next fiscal year." That version tells a firm what the final deliverable has to support.

Be honest about history and constraints, such as limited internal bandwidth or a past study whose recommendations were never implemented. State what data and which people the firm will have access to, because both shape the approach and the price.

What responders see: firms make their go/no-go call from this section. A brief built around a specific decision attracts firms that have helped other clients make that decision before.

Define the scope, deliverables and acceptance criteria

Set two or three objectives and a measure of success for each, such as a costed roadmap approved by the steering group by a set date. Then write an explicit in-scope and out-of-scope list. The out-of-scope items stop firms from pricing work you never meant to buy.

Pair every deliverable with an acceptance criterion covering format, review rounds and who signs off. For example:

Deliverable 3, current-state assessment. Accepted when delivered as a slide report of no more than 40 pages plus a data appendix, revised after one round of consolidated steering group comments, and signed off by the CFO.

Describe the outcome you need and leave the method open. The firms you invite have solved similar problems, and how they would approach yours is part of what you are scoring.

Measurable deliverables also give you something to point to when the spend is questioned. In a June 2025 letter on the GSA consulting contract review, the U.S. General Services Administration (GSA) wrote that "GSA has been leading an administration-wide review of Federal consulting contracts; this effort has so far resulted in savings of $23.3 billion in multi-year awards through the termination of contracts."

What typically goes wrong here: you over-prescribe the method and get your own plan back, priced five ways. Or you leave the scope vague, each firm prices its own assumptions, and the prices cannot be compared. You can spot either problem when proposals list very different assumptions or when bidders send a long run of scope questions.

Specify the team and experience you want to see

In consulting you are buying specific people, and "provide CVs of key staff" produces answers you cannot compare. Federal source selection rules list personnel qualifications and prior experience among the non-cost factors an agency can evaluate.

Three requirements make the team section comparable: named key personnel, one resume format and project references you can check. The counts and page limits below are your choices, not industry standards.

What to requestFormat to requireWhy it makes proposals comparable
Key personnel list with allocationOne row per role you define, with name, percent allocation or hours, and locationEvery firm answers against the same roles, person for person
One resume per named roleYour template or field list, a page limit you set, same order as the role listScorers find the same facts in the same place in every proposal
Project referencesA number and recency you choose, fixed fields, named team members on eachExperience claims tie back to the people you are buying
Client reference contactsName, title and contact details for someone who has agreed to be called, linked to a reference projectYou can confirm dates and roles at shortlist stage
Team organization chartOne page showing named people, reporting lines and where your own staff fitYou see each firm's structure in the same form
Substitution termsSigned acceptance of your clause on key personnel changesEvery firm makes the same staffing commitment

Ask for named key personnel, not a bench

List the roles you need, such as an engagement lead, a lead per workstream and any named specialists. Require one named person per role, with percent allocation or hours and location (on-site or remote). The engagement lead should be someone who will do the work week to week, not only the partner who sells it.

Add a substitution clause that allows no change to key personnel without your written approval and requires any replacement to have equal or better qualifications. That clause protects you from bait and switch, where the senior names in the proposal disappear after award. Ask for an organization chart of the proposed team as well.

What responders see: a role list tells the bid team exactly whose resume to tailor. "Include all relevant staff" gets you a generic bench of CVs.

Set one resume format and map every resume to a role

Provide a resume template or a fixed field list:

  • name and proposed role on this engagement
  • allocation, matching the key personnel list
  • relevant certifications
  • a small set of relevant projects (you choose the number), each with client type, the person's own role, dates and outcome

Set a page limit per resume, for example two pages, and apply it to every firm. Ask for one resume per named role, in the same order as your role list, with no extras.

Firms that bid regularly are used to this. Funders and agencies already prescribe standard bid resume formats. For federal A-E (architect-engineer) work, Section E of the SF 330 (Standard Form 330, Architect-Engineer Qualifications) standardizes resumes of key personnel.

What responders see: with a fixed format, the bid team spends its hours tailoring content to your problem instead of reformatting layouts.

Ask for project references you can check

Set the number and recency you want, for example four projects completed in the last five years. Then fix the fields: client, scope, contract value range, dates, outcome, the names and roles of proposed team members who worked on the project, and a reference contact who has agreed to be called. Named people on each project tie the firm's experience claims back to the team you are buying.

Plan to spot-check at shortlist stage. Call the contacts and confirm that the dates and roles they describe match the resumes.

Section F of the SF 330 covers example projects and is a good model. The official SF 330 instructions say "Present ten projects, unless otherwise specified by the agency." For each key person, they ask firms to "Provide information on up to five projects in which the person had a significant role that demonstrates the person's capability relevant to her/his proposed role in this contract." They also leave limits to the buyer: "Individual agencies may supplement these instructions. For example, they may limit the number of projects or number of pages submitted in Part I in response to a public announcement for a particular project."

When selection is qualifications-based

AEC buyers and many public agencies use QBS (qualifications-based selection). They rank firms on qualifications first, then negotiate a fair price with the top-ranked firm. Federally this comes from the Brooks Act, and the federal qualifications-based selection rule in the FAR (Federal Acquisition Regulation) requires contracts to be negotiated "based on the demonstrated competence and qualifications of prospective contractors to perform the services at fair and reasonable prices." In a QBS RFQ or SOQ (statement of qualifications), the team and project sections decide the award.

Federal A-E buyers follow the SF 330 Part I requirement: "Use the SF 330, Part I-Contract-Specific Qualifications, to obtain information from an architect-engineer firm about its qualifications for a specific contract when the contract amount is expected to exceed the simplified acquisition threshold." For the current simplified acquisition threshold, FAR 2.101 states that "Simplified acquisition threshold means $350,000," with a short list of exceptions. Many states and municipalities have QBS laws of their own. For how firms build Sections E and F under this kind of scoring, see the SF 330 guide for AEC firms.

Tell firms exactly what to submit and in what format

Give firms a fixed list of sections in a fixed order. You can adapt this outline:

  1. Executive summary
  2. Understanding of the problem
  3. Approach and work plan
  4. Team and key personnel
  5. Project references
  6. Risks and assumptions
  7. Pricing, in a separate file using your pricing template
  8. Required declarations, including conflicts of interest

Set a page limit for the main body, for example 20 pages, and put full resumes and reference sheets in appendices so they do not compete for that space. State the file format, the submission method and the deadline with its time zone. Order the sections to mirror your evaluation criteria so each scorer finds what they score in the same place in every proposal.

What responders see: the bid manager builds a compliance matrix from these instructions, line by line. When the instructions and the scoring criteria disagree, you get clarification questions or proposals that are non-compliant on a technicality.

Choose a pricing model and share your budget range

Use a fixed fee for well-defined deliverables and T&M (time and materials) with a ceiling when the scope is uncertain. Reserve outcome-linked fees for outcomes you can measure. Ask for a rate card by role that ties to the named team, so you can check the price against the staffing plan. Share a budget range, or at least an order of magnitude. Without one, you get proposals sized for different engagements, from a six-week diagnostic to a year-long program. Under QBS, price is negotiated after ranking, as described in the team step.

Public buyers spend heavily in this category, which is one reason the pricing approach has to hold up to scrutiny. A U.S. Government Accountability Office review of federal consulting obligations since 2019 found that "From fiscal years 2019 through 2023, federal agencies obligated over $500 billion on contracts associated with consulting services."

Set a timeline and Q&A rules that allow tailored responses

For example, a calendar for an engagement with five named roles might run like this (an illustration, not a standard):

  • Week 0: RFP released
  • Week 1: intent-to-bid due
  • Week 2: question deadline
  • Week 3: answers published to all bidders
  • Week 6: proposals due
  • Weeks 8 and 9: shortlist and orals with the named team
  • Week 10: award
  • Week 12: engagement starts

Name one point of contact, and publish every question with an anonymized answer to all bidders.

Size the response window to the work you asked for in the team step. Every named role means a tailored resume, and every reference means a project sheet someone has to update and get approved. A standard federal form already takes real effort. The SF 330 instructions state, "We estimate that it will take 29 hours (25 hours for part 1 and 4 hours for Part 2) to read the instructions, gather the facts, and answer the questions." Your RFP adds an approach and a price on top of that.

What typically goes wrong here: a two-week window, perhaps over a holiday, for ten tailored resumes and five project sheets. Good firms decline, or they send recycled generic CVs. The warning signs are a low intent-to-bid count and late questions about format.

Invite only as many firms as your panel can evaluate properly, and commit to debriefing every respondent.

What responders see: a realistic window and a short invitation list tell a bid team the tailoring is worth the effort, so the resumes you receive are written for your engagement.

Publish the evaluation criteria and weights up front

Give each criterion a weight and a scoring scale with defined levels. On a 1 to 5 scale, for example, 3 might mean the requirement is met and 5 that it is exceeded with evidence. Split "team" into named-personnel quality and relevant project experience so neither is scored on impression.

The weights below show the structure. They are an illustration, not a benchmark.

CriterionIllustrative weightScored from
Understanding of the problem and approach25%Sections 2 and 3
Named personnel quality20%Section 4 and resume appendix
Relevant project experience15%Section 5 and reference appendix
Work plan and risk15%Sections 3 and 6
Price25%Pricing file

For the experience criteria, the A-E evaluation criteria in the FAR offer a tested model, including "Past performance on contracts with Government agencies and private industry in terms of cost control, quality of work, and compliance with performance schedules."

Have each panel member score independently before a consensus meeting. Hold orals with the named team, not only the sales lead, and ask each key person to walk through a project from their resume. State your tie-breaker in advance, and spot-check references before award.

What responders see: when weights are missing, every firm guesses where to spend its effort, and each guesses differently. Published weights tell a bid team where to put its best people and strongest projects.

Settle IP, data protection and conflicts of interest

State who owns the work product and any intellectual property (IP) created during the engagement, and what knowledge transfer you expect at the end. Set out your confidentiality and data-protection requirements. Attach the draft contract or its key terms, and ask firms to list any exceptions in one place in the proposal, so legal reviews them before award and not after. State your conflict rule, for example whether a firm that writes the strategy may bid on implementation, and require every firm to disclose actual or potential conflicts.

What changes in an RFP for IT consulting services

The structure above still applies. IT work needs more precision about your technology and the people who know it.

  • Describe your current architecture and tech stack, including key systems, integrations and hosting, so firms can staff the right skills.
  • Ask for a named architect for each technology in scope, with certifications and the dates they were earned or renewed.
  • Match the skills you ask for to your stack. A requirement for generic "cloud experience" lets almost any resume qualify, so name the platforms you actually run.
  • State which systems and data the firm will touch. Where relevant, ask firms to state security certifications such as ISO 27001 or to provide SOC 2 reports.
  • Specify the delivery model you can work with (onshore, nearshore or offshore) and the time-zone overlap you need.

On pricing, a fixed fee usually fits well-defined implementation phases, while T&M with a ceiling suits discovery. Treat knowledge transfer and handover to your internal team as a deliverable with its own acceptance criterion, the same as any other.

What your team requirements cost the firms answering them

A well-built RFP asks each firm for role-mapped, tailored resumes and project references in a fixed format. Firms that keep resumes in SharePoint folders and old Word files build that package by hand, chasing consultants for updates the week the RFP lands. That is why short windows produce generic answers. Buyers get stronger responses from firms whose people and project data is already current, and bid managers can treat the spec table above as the requirement set to prepare for.

Flowcase is the system of record for people and project experience. It keeps resumes and project sheets as structured records maintained by the people who own them, so a bid team can find, tailor and export them into the firm's template or an SF 330. In a Flowcase user survey, 56% of surveyed users reported saving over 50 hours per month.

Read your draft the way a bid manager will

Before release, give the draft to someone who has answered RFPs and ask them to build a response plan in 30 minutes. The plan should list every document they would produce, who would produce it and how long it would take. Anything they have to guess at will come back to you as a clarification question or as five different interpretations.

Then check two mappings: every evaluation criterion points to a submission section, and every named role points to a resume slot. You will know the RFP worked when the Q&A log has few questions about format and team, and the panel can score the proposals side by side on team and experience in one sitting.

If your firm answers RFPs like this one, see how Flowcase keeps resumes and project sheets ready for them. Book a demo.

Keep reading

Your firm knows what wins bids. It just can’t find it in time.

Sales and Marketing
Productivity

The AI Proposal Assistant is here, and it runs on your live data

News

12 Best AI Tools for Engineers in 2027

No items found.