If you sell into businesses or into the public sector, you will fill in DDQs, PQQs and RFIs at different points in a deal cycle. They are not interchangeable. The same answer copy-pasted between formats either over-shares, under-shares, or misses the buyer's actual question. This piece walks through the three, what each is really asking, and the response patterns that work.
RFI: requests for information
An RFI is pre-procurement. The buyer is mapping the market and learning what suppliers look like. There is usually no contract attached to the document itself. The point of an RFI for the buyer is to shape the eventual tender specification, the eventual framework lots, or the eventual shortlist.
What the buyer is really asking: are you a credible candidate for the kind of thing we are about to buy, and do you have anything we should factor into the eventual tender design.
What the right response looks like:
- Concise. RFIs respect time. A two-page response often beats a twelve-page response.
- Specific to the buyer's stated context. Generic capability statements get filtered out.
- Honest about scope. If the eventual tender as described would not be a fit for your business, say so. Buyers remember who is straight with them.
- Suggests refinements where appropriate. Buyers often genuinely want input on lot structure, evaluation weighting, or specification clarity.
RFIs are low-effort but high-signal: if you do not show up at this stage, you do not get factored into the procurement design.
PQQ: pre-qualification questionnaire
A PQQ (now usually called a Selection Questionnaire under the Procurement Act 2023) is the formal selection stage of a UK public sector procurement. The buyer is checking the bidder meets the minimum bar: financial standing, accreditations, insurances, exclusion grounds, technical and professional capacity. PQQs are pass-or-fail. They do not award the contract.
What the buyer is really asking: are you legally and operationally credible enough that we should let you bid on the actual contract.
What the right response looks like:
- Complete and current. Missing an ISO certificate scan or quoting an expired Cyber Essentials cert is a fail.
- In the format requested. PQQs are rule-bound. Word counts, file types, and answer slots are not suggestions.
- Conservative on risk-laden questions. Past contract terminations, financial standing, modern slavery: answer precisely, evidence with documents, do not editorialise.
- Built from a reusable credentials library. Most PQQs ask the same selection-stage questions in the same shapes. A library that holds your current insurances, accreditations, accounts and standard case studies turns a PQQ into a fifteen-minute review.
PQQs are the place to make sure nothing trivial costs you the chance to bid. If you fail at PQQ, the quality of the eventual tender response does not matter.
DDQ: due diligence questionnaire
A DDQ is a deeper, more commercial document. It is most commonly used by investors evaluating a target company, by acquirers in M&A, by partnership teams in framework agreements, and by some procurement functions for high-stakes purchases. The questions cover commercial, financial, legal, technical, and increasingly ESG and information security topics.
What the asker is really asking: is the picture you have shown us at term sheet or letter of intent stage actually true at the level of detail.
What the right response looks like:
- Sourced. Every claim should be traceable to the data room. Numbers come from board packs, customer counts from CRM, contracts from the legal folder.
- Function-routed. Finance answers the finance questions, legal the legal ones, the CTO the technical ones. The DDQ should never go to one person to fill in alone.
- Stable over time. The same DDQ may be answered for three different parties in a sale process. Build the answers once, version them, and update the diff each time.
- Honest about gaps. A DDQ flushes out the things the data room does not yet show. Surface the gaps, do not hide them, because the diligence team will find them anyway.
DDQs sit at the highest end of the effort scale. They are not the place to retype. They are the place to retrieve from a well-structured data room, with the right people approving the answers in their area.
The common thread: one evidence library, three views
The right structural answer to all three documents is the same: a single internal evidence library with the controls, credentials, accounts, contracts, case studies and policies indexed. Each of the three response types is a different view onto that library, written for a different audience, with a different appropriate level of detail.
The wrong structural answer is to maintain three separate folders of "RFI answers", "PQQ answers" and "DDQ answers". When the source evidence updates, you have three copies to refresh, and one of them will silently drift. The wrong copy will be the one that gets sent.
How Bidwell handles the three together
Bidwell is the drafting layer on top of one shared evidence library. The same library that holds your ISO certificate scan, your last three years of accounts, your standard case studies and your security controls feeds the drafted response for every RFI, every PQQ and every DDQ that lands. The audience-specific framing is applied at draft time, not stored as three copies of the same fact.
The practical effect is straightforward: the second RFI takes twenty minutes instead of two hours. The third PQQ takes ten minutes instead of two hours. The DDQ that lands the day after term sheet has 80 per cent of the answers already drafted because the data room is already indexed.
If you have stalled on a deal because the DDQ has been sitting on the founder's desk for a week, the practical move is to index the data room before drafting any answers. Once the index exists, the answers largely write themselves.
