Staffing
11 min Read

IT Staffing RFP Guide: Template, Questions to Ask and Vendor Scorecard

Mayank Pratap Singh
Mayank Pratap Singh
Co-founder & CEO of Supersourcing

Most IT staffing RFP awards go to the vendor best at hiding its markup. The typical request asks for a bill rate by role, scores it at 40–60% of the total, and never asks for the pay rate underneath, so a response quoting $95 an hour with a 65% markup beats one quoting $98 with a 40% markup and a better engineer. The buyer selects the cheaper number and gets the weaker person.

That is why a well-built IT staffing RFP is a procurement tool first and a pricing tool second. In the requests the Supersourcing delivery team responds to, the ones that produce good outcomes share five features: volumes and seniority by quarter, pay rate and markup as separate lines, SLAs in numbers, a question about who audits the vendor’s AI screening tools, and a published scoring weight before the first proposal arrives. The ones that go wrong skip at least three of the five.

The 2026 market makes this more expensive to get wrong. A net 35% of IT staffing firms reported rising bill rates in the three months to September 2026, margins are widening in IT while flat elsewhere, and AI-screening and pay-transparency laws now put compliance obligations on the buyer as well as the vendor. An RFP written on a 2023 template misses all three.

This guide gives you the full IT staffing RFP template section by section, 25 vendor questions grouped by stage, a 100-point weighted scorecard, and a seven-week process timeline. Copy the pieces you need; the structure works for three contract seats or a 200-seat preferred-supplier programme.

Staffing Industry Analysts reports that a net 35% of IT staffing firms saw rising bill rates and a net 29% saw rising gross margins in the three months to September 2026, with “demand for IT workers running ahead of supply.”

TL;DR

This guide is for procurement, talent-acquisition and engineering leaders who need to issue an IT staffing RFP and choose a vendor on evidence rather than a bill rate. It includes a copyable staffing RFP template, 25 questions by stage and a weighted scorecard.

The biggest number: markups on contract IT seats run 40–65% over pay, so an RFP that scores bill rate without asking for pay rate can award a contract to a vendor paying its engineers 20% less for the same price.

By the end you will be able to issue an IT staffing RFP in a week, shortlist in three, and defend the award to a CFO with a scorecard rather than a gut call.

 

What Is An IT Staffing Rfp?

An IT staffing RFP is a formal request for proposal that a company issues to staffing vendors to source contract, contract-to-hire or dedicated technology talent. It sets out roles, volumes, locations and engagement models, requires a rate card with pay rate and markup disclosed, defines service levels and compliance obligations, and states how responses will be scored before vendors submit.

The “before vendors submit” part is the test of a real RFP. If the weighting is decided after the proposals are read, it is a beauty contest with paperwork.

The Core Problem: Rfps That Score The Wrong Things

Three failures recur in the IT staffing RFP documents we respond to. First, rate-only scoring: 40–60% of the weight on bill rate, nothing on pay rate, markup, time-to-shortlist or retention, so the lowest number wins regardless of who is actually delivered. Second, too many vendors: 15–20 invitees produce 15–20 near-identical responses and an evaluation that takes six to eight weeks, during which the roles stay open. 

The field is also consolidating, with 57 firms generating $27.4 billion in US IT staffing revenue and the top five taking a disproportionate share, so a long list adds subsidiaries of the same groups, not choice. Third, no numbers in the SLA section: “prompt replacement” and “quality candidates” cannot be scored or enforced.

The cost of those failures is measurable. Markups on contract IT seats sit at 40–65% over pay in the current market, so two vendors at the same bill rate can be paying engineers 15–20% apart. A role that stays open through an eight-week IT staffing RFP evaluation costs the velocity of the team it was meant to join, in a year when Gartner expects IT spending to grow 15% to $7.35 trillion and senior supply to stay short. And a contract with no replacement SLA turns every mis-hire into a four-to-six-week restart.

The template below fixes all three by construction: it forces the pay-markup split, caps the invitee list through an RFI, and puts every SLA in a number. The list of mistakes made when choosing an IT staffing partner covers what happens when the IT staffing RFP skips them.

RFP Vs RFI Vs RFQ For Staffing: Which One You Actually Need

The three documents answer different questions, and issuing the wrong one is the most common reason an RFP for staffing services runs long.

Document Question it answers Use it when Typical cycle
RFI (request for information) Who is capable and worth inviting? You have 15+ possible vendors and need to cut to 5–8 1–2 weeks
RFP (request for proposal) How would you deliver, at what rate, under which terms? You have a defined scope and want a scored, defensible award 5–7 weeks
RFQ (request for quotation) What is your price for exactly this? Scope and terms are fixed and only price is open, such as a renewal 1–2 weeks

Run an RFI first if your list is longer than eight vendors. Issue an RFQ, not an IT staffing RFP, for a renewal where the only open item is the rate card; re-running a full RFP on an incumbent you intend to keep costs weeks and buys nothing.

The IT Staffing RFP Template, Section By Section

This is the longest section, and it is the document itself. Each of the ten sections below is a heading in the IT staffing RFP you issue, with what to write under it and the one line vendors most often exploit when it is missing. Numbered so the whole thing can be copied as an outline.

  1. Company context and objectives. Two paragraphs: what you build, the size of the engineering organisation, and the business reason for the requirement (a product launch, a GCC ramp, a backlog). State whether you are buying a one-off fill, an ongoing supply or a preferred-supplier position. Vendors price risk; the more they know, the sharper the quote.
  2. Scope and volumes. A table of roles by seniority, location and start month, with a 12-month forecast of seats (even if labelled indicative). Include tech stack, overlap hours required and whether seats are remote, hybrid or onsite. Missing volumes are the single biggest reason rate cards come back padded.
  3. Engagement models required. Specify which contract, contract-to-hire, dedicated team or statement-of-work you will buy, and whether vendors may propose alternatives; the contract-to-hire staffing model deserves its own line because its conversion fee is where margin hides. The IT staffing contract models explainer sets out the trade-offs; the contract IT staffing page shows what a contract and C2H seat looks like from the vendor side.
  4. Rate card format and markup disclosure. Mandate a three-column rate card per role and band: pay rate, markup percentage, bill rate. Require conversion fees for contract-to-hire as a schedule by month of conversion, and require that all platform, payment and currency fees be inside the bill rate. This section of the IT staffing RFP is the one that saves the most money; the bill rate vs pay rate breakdown explains why.
  5. Sourcing and vetting process. Ask for the vendor’s process in stages with a pass rate at each stage, the technical assessment used for each role family, and whether assessments are run by engineers or recruiters. A credible answer looks like the five-stage IT staffing agency vetting process; a vague one is a résumé database.
  6. Service levels. Put every SLA in a number: median working days to interview-ready shortlist (ask for the vendor’s last-12-month actual), submittal-to-interview ratio, offer-acceptance rate, 90-day retention, replacement window in working days and the credit if it is missed. A 7–10 working-day shortlist and a 7–10 day replacement are achievable benchmarks; the SLAs from an RPO provider list translates well to an IT staffing RFP.
  7. Compliance and data. Require: worker classification approach (W2, C2C, 1099 in the US; contractor vs payroll in India) and who carries employer liability; I-9/E-Verify and background-check standards; a list of every automated or AI screening tool used on your candidates and its most recent bias audit, which NYC Local Law 144, Illinois HB 3773 and the Colorado AI Act now make a buyer-side exposure; pay-transparency compliance for postings in covered states; candidate-data handling under the DPDP Act in India and GDPR where relevant; and insurance certificates.
  8. IP, confidentiality, non-solicit and conversion. State that IP assignment and NDA flow down to every placed engineer, define the non-solicit period both ways, and set conversion fees in this section rather than leaving them to the MSA. Vendors that resist flow-down are telling you something.
  9. Reporting and governance. Monthly: open roles, days-to-shortlist, submittals, interviews, offers, starts, attrition, rate variance against card. Quarterly business review with a named account lead. Ask for a sample report, not a promise of one; accept promises here and you get promises for the length of the contract.
  10. Commercial terms and submission format. Contract length, rate-lock period, indexing mechanism for mid-term reviews, payment terms, termination for convenience, and the exact response format (page limits, mandatory tables, question numbering). State the scoring weights here, in the document, before responses are due; the negotiating RPO contracts guide covers the terms that move most in the final round, and they are the same terms here.

An IT staffing RFP with those ten sections typically runs 8–12 pages and takes two to four working days to draft from this outline. It also reduces the responses you receive, because vendors who cannot fill section 4 or section 7 stop responding, which is the point.

25 Questions To Ask A Staffing Agency, Grouped By Stage

These questions to ask a staffing agency go into the IT staffing RFP as a numbered annex so every vendor answers the same list in the same order, which is what makes scoring possible. They are grouped by the stage at which each matters, and the three marked “Score this” carry the most weight in the scorecard that follows.

Capability (questions 1–7)

  1. How many IT contract placements did you make in the last 12 months, by role, family and seniority?
  2. What share of those were in our stack and our locations?
  3. How large is your active, pre-vetted bench for our top three roles today, and when was it last refreshed?
  4. Which engagement models do you deliver, and which do you decline?
  5. Who are three current clients with a similar volume and stack, and may we speak to them?
  6. What is your account team’s ratio of recruiters to engineers running technical assessments?
  7. What are the three roles you would advise us not to source through you, and why?

Delivery (questions 8–14)

  1. What was your median working days from job description to interview-ready shortlist over the last 12 months? (Score this.)
  2. What is your submittal-to-interview ratio and interview-to-offer ratio?
  3. What is your offer-acceptance rate and 90-day retention on contract placements? (Score this.)
  4. Describe your technical assessment for a senior engineer in our primary stack, including who conducts it and the pass rate.
  5. What is your replacement window in working days, and what credit applies if it is missed?
  6. How do you handle a candidate who no-shows on the start date?
  7. Which automated or AI tools touch candidates in your process, and who audited them last?

Commercial (questions 15–20)

  1. Provide the rate card as pay rate, markup and bill rate per role and band. (Score this.)
  2. Which fees sit outside the bill rate, if any?
  3. What is your conversion-fee schedule for contract-to-hire by month of conversion?
  4. What rate lock do you offer, and what index governs the mid-term review?
  5. What volume discount applies at 10, 25 and 50 concurrent seats?
  6. What is your payment term, and what early-payment discount do you offer?

Compliance and exit (questions 21–25)

  1. How are workers classified in each of our locations, and who carries employer liability?
  2. Provide your background-check standard, I-9/E-Verify process and insurance certificates.
  3. How do you comply with pay-transparency and AI-in-hiring rules in the states and countries we hire in?
  4. How is candidate data stored, for how long, and under which consent basis?
  5. On termination, what transfers to us: candidate pipeline, assessment records, placed engineers’ contracts?

The Staffing Agency Evaluation Scorecard: 100 Points, Weighted Before You Read A Proposal

The staffing agency evaluation scorecard is the part of the IT staffing RFP that turns 25 answers into a defensible award. Publish the weights in section 10, score each criterion 1–5, multiply by the weight, and total. The six IT staffing vendor selection criteria below reflect what predicts a good outcome in the engagements we have delivered; adjust the weights, but publish the adjustment.

Criterion Weight What a 5 looks like What a 1 looks like
Delivery evidence (days-to-shortlist, fill rate, retention, all last-12-month actuals) 25 7–10 working days, 90%+ 90-day retention, data provided “Fast,” “high quality,” no numbers
Vetting rigour (assessment design, who runs it, pass rates) 20 Engineer-run practical assessment with stated pass rate Keyword screen and a recruiter call
Commercial transparency (pay/markup/bill split, fees inside rate, conversion schedule) 20 Three-column card, nothing outside the rate, schedule by month Bill rate only, fees “on request”
Compliance and data (classification, AI-tool audit, pay transparency, DPDP/GDPR) 15 Documents attached, audits dated 2026 Statements of intent, no documents
Bench and stack fit (active pool in our roles and locations) 10 Named pool size, refreshed within 90 days “Access to millions of profiles”
Governance and references (reporting sample, account lead, reference calls) 10 Sample report, named lead, three reachable references Generic deck, references “on award”

Total the six lines. In our experience a spread under five points between the top two is a tie; break it with a paid one-week trial on one live role rather than another presentation round. Rate sits inside the commercial-transparency line deliberately: at 20 points it matters, but it cannot outvote delivery evidence and vetting rigour combined.

How To Run The Process: A Seven-Week It Staffing RFP Timeline

The timeline is as important as the document. The steps below assume a shortlist of five to eight vendors; stretch step 1 if you are starting from a long list.

  1. Week 0: RFI to cut the list. One page, eight questions, one-week turnaround. Invite only vendors who can answer questions 1–3 and 8 with numbers.
  2. Week 1: Issue the IT staffing RFP. Ten sections, 25-question annex, published weights, a single Q&A deadline.
  3. Week 2: Vendor Q&A. Collect questions in writing, answer all vendors identically, and treat the quality of questions as a signal.
  4. Week 3–4: Responses due; score blind. Two evaluators score independently against the weights before any discussion; reconcile only the lines that differ by two points or more.
  5. Week 5: Finalist presentations, with a twist. Give each finalist one live job description and 48 hours; score the shortlist they return, not the slides.
  6. Week 6: Paid trial week. The top vendor places one engineer on a real ticket for one paid week with a defined deliverable.
  7. Week 7: Award and MSA. Carry the rate card, SLAs and conversion schedule from the RFP response into the contract as exhibits, so the proposal is the contract.

Step 5 is where most awards actually get decided. Vendors that return a credible shortlist in 48 hours have the bench they claimed; the ones that ask for two weeks do not.

Two RFP’s, Anonymised

US SaaS, 40-seat contract programme. A Series D SaaS company ran its 2026 IT staffing RFP on a rate-only template, awarded to the lowest bill rate, and saw 90-day attrition above 30% in the first quarter. The re-run used the ten-section template, the pay-markup split and the scorecard above; the winning response was 4% higher on bill rate, 11% higher on pay rate, and 90-day retention on the programme ran above 90% in the following two quarters. The difference was entirely in which number was scored.

Indian fintech GCC, preferred-supplier panel. A GCC consolidating 14 staffing vendors to a panel of four issued an RFI, cut to seven, and ran the seven-week IT staffing RFP process with a 48-hour live-requisition round. Two vendors withdrew at the rate-card stage rather than disclose markup; the final panel’s blended markup came in roughly a fifth under the previous average, and median days-to-shortlist fell from more than four weeks to under ten working days across the panel. The pattern: markup disclosure removes the vendors you did not want anyway.

What Most Teams Get Wrong

They score the bill rate in an IT staffing RFP and forget that it is two numbers. An IT staffing RFP that does not force pay rate and markup apart will award to the vendor paying its engineers least, because that is how a low bill rate is produced. Score delivery evidence and vetting rigour above rate, require the split, and run one paid trial week; the rate you pay will be within 5% either way, and the engineer you get will not.

Pressure-Test Your RFP Before It Goes Out

If you have a draft IT staffing RFP, or a 2026 renewal you are about to run as an RFQ, send it to mayank@engineerbabu.com before it goes out. 

Supersourcing has responded to and delivered against staffing RFPs for US product companies and Indian GCCs for 10+ years across 527+ projects, and will return a redline against the ten sections above, a sample three-column rate card for your roles across onsite developers, remote developers and dedicated development teams, and the recruitment process outsourcing option if your volumes justify capacity by the month instead of per seat. 

Terms for India-delivered seats are on the IT staffing company in India page, and the contact form is at https://supersourcing.com/contact-us/.

FAQ

What should be included in a staffing RFP?

Ten sections: company context and objectives; scope and volumes by role, seniority and month; engagement models; a rate card with pay rate, markup and bill rate; sourcing and vetting process; numeric SLAs; compliance and data handling, including AI screening tools and pay transparency; IP, NDA, non-solicit and conversion fees; reporting and governance; and commercial terms with the scoring weights published.

How do you evaluate staffing agency proposals?

Score each proposal against weights published in the IT staffing RFP, with delivery evidence and vetting rigour together worth more than price, scored blind by two evaluators before discussion. Break near-ties with a 48-hour live requisition and a paid trial week rather than a second presentation round. The IT staffing agency fees benchmarks show what a fair commercial line looks like.

How long should an IT staffing RFP process take?

Five to seven weeks from issue to award for a five-to-eight-vendor shortlist: one week to issue, one for Q&A, two for responses and blind scoring, one for live-requisition presentations, one for a paid trial, one for award and MSA. Add one to two weeks at the front for an RFI if you are starting from more than eight vendors.

How many vendors should you invite to an IT staffing RFP?

Five to eight after an RFI. Fewer than five gives too little rate and capability spread; more than eight produces near-identical responses and an evaluation that runs six to eight weeks. For a panel, award to two to four, with at least one India-delivery specialist alongside US generalists if offshore seats are in scope.

What is a reasonable markup to expect in RFP responses?

Markups on contract IT seats generally sit at 40–65% over pay in the 2026 market, lower at volume and for long-tenure dedicated seats. The IT contract staffing cost breakdown shows what sits inside the markup; the IT staffing rate card India gives bands for India-delivered seats so you can sanity-check responses.

Should an RFP ask for bill rates or pay rates?

Both, on the same line, with the markup between them, so vendors cannot win by paying engineers less. If you want a sample three-column rate card for your roles before you issue, or a review of a draft IT staffing RFP against the scorecard above, the IT staffing company in USA team will return it with the benchmarks filled in rather than a pitch.

Author

  • Mayank Pratap Singh - Co-founder & CEO of Supersourcing

    With over 11 years of experience, he has played a pivotal role in helping 70+ startups get into Y Combinator, guiding them through their scaling journey with strategic hiring and technology solutions. His expertise spans engineering, product development, marketing, and talent acquisition, making him a trusted advisor for fast-growing startups. Driven by innovation and a deep understanding of the startup ecosystem, Mayank continues to connect visionary companies and world-class tech talent.

    View all posts

Related posts