Proposal, tender, and questionnaire review

Frequently asked questions

Everything you need to know about ReqFit, from how reviews work to what we do and don't analyse.

Security

Documents are processed in memory on Google Cloud Platform using Vertex AI. Static customer administration data (account profile, credit balance, retained requirements lists, report records) resides within European cloud infrastructure. Transient text extraction for AI inference may be routed securely across dynamic international regions selected for capacity and performance, governed by our Data Processing Agreement and the UK Extension to the EU-US Data Privacy Framework. Enterprise customers with specific data residency requirements can discuss these with us on request.

Your proposal documents and the buyer's requirements document are purged from runtime memory immediately after the report is delivered. The structured requirements list extracted from the buyer's document is retained against your account so that re-running a review on an improved proposal is measured against the same fixed set of requirements. You can delete your account at any time, which removes all retained data including stored requirements lists.

Reports are kept in your account, viewable online with PDF and DOCX download available throughout, for ninety (90) days from generation. You can delete a review manually at any point within that window. After 90 days, reports are deleted automatically. We encourage you to download your reports while they are available; downloaded copies remain on your own device after our retention window ends.

No. Your documents are processed via Google Cloud Vertex AI under Google's Service Specific Terms, which restrict use of your prompts and outputs for AI model training. They are used only to produce your review report, are not logged or retained by the platform after the report is generated, and are not used to improve any AI model, ours or anyone else's.

Documents are processed automatically with no human review at ReqFit. Customer support staff have no access to document content. Reports are visible to you and to any colleagues you have invited into your organisation through admin settings (see "How do team accounts handle data access?" below for detail). Reports are not visible to users outside your organisation.

Yes. ReqFit is operated by CASM Labs Ltd, registered with the UK Information Commissioner's Office under registration ZC111039 and bound by UK GDPR and the Data Protection Act 2018. Our standard Data Processing Agreement applies automatically when you create an account. A bilateral signed copy is available on request for enterprise procurement. Read our plain-English UK GDPR statement for the full picture.

Account deletion removes all retained data associated with your account, including stored requirements lists from previous reviews, account configurations, and any reports still within their 90-day retention window. Reports you have already downloaded remain on your own device. Account deletion is permanent.

Our standard Data Processing Agreement is published and applies automatically when you create an account. If you need a bilateral signed copy for your procurement or vendor onboarding process, contact us at security@reqfit.com and we will send you a Word version for execution. We can also countersign a DPA you provide, whichever is faster for your process.

Not yet. SOC 2 Type 2 and ISO 27001 both take time to obtain properly, requiring an established track record of operation rather than a point-in-time check, and we are working towards them honestly rather than marketing them aspirationally. Our underlying platform (Google Cloud) holds SOC 2, ISO 27001, and ISO 27018, and we hold Cyber Essentials certification, awarded on 27/05/2026 and valid to 27/05/2027, as our immediate trust signal.

If we identify a security incident affecting your data, we will notify you within 48 hours of detection, as set out in Clause 6 of our Data Processing Agreement. UK GDPR also imposes breach notification obligations, and our process is designed to meet them. The notification will include the nature of the incident, the categories of data affected, the likely consequences, and the measures we are taking. To report a suspected vulnerability or security concern, contact security@reqfit.com.

Team access is invite-only. The account owner invites colleagues into their organisation through admin settings; once a colleague accepts, team members can see each other's reviews. This supports workload sharing, peer review, and holiday cover. There is no automatic same-domain grouping, and reviews are never shared across organisations or with other ReqFit users.

Getting started

Yes. Create an account, upload your documents, and receive a complete review at no cost. No credit card required. Your free review must be used within 7 days of creating your account, after which it expires.

PDF, Word and PowerPoint documents. Both the RFP and the proposal should be uploaded as one of these formats.

Reviews run end to end without your input. The exact time depends on document length, a typical review takes around 10 to 15 minutes but larger proposals will take longer. We send you an email to your results page the instant your review is generated so you don't need to wait around.

Yes. A free account gives you access to your first review at no cost. No credit card is required to sign up.

Yes. ReqFit works with any RFP, ITT, tender, procurement document, or due diligence questionnaire where there are stated requirements or questions that your response needs to address. It is sector-agnostic.

Yes. A due diligence questionnaire is a structured set of questions, which is exactly the kind of document ReqFit checks against. Upload the questionnaire in whatever format it comes in, then upload your completed responses along with any attachments your answers refer to. ReqFit works through it question by question and shows you which questions your responses cover and which still need attention before you return it. It checks how well your responses cover what is asked. It does not judge whether your answers will satisfy the assessor.

Reviews and analysis

ReqFit works through the requirements in your RFP and maps each one against your proposal to determine whether it has been addressed. You receive a requirement-by-requirement breakdown, a coverage score, and specific guidance on where gaps exist.

Your coverage score is a percentage that reflects how many of the stated requirements in the RFP have been addressed in your proposal combined with how strong your response to each is. A higher score means fewer gaps for evaluators to penalise.

Improved your proposal and want to re-check it? Log in to reqfit.com, open the results screen for your original review, and choose "Re-run with new draft" from there. Re-running has to be done from that results screen in your account, not from a downloaded PDF or Word copy of the report. Your updated proposal is then scored against the same requirements as your first review, so both reports share the same requirement IDs and you can see exactly which gaps you have closed. A re-run uses one review credit. Avoid starting a brand-new review for an updated proposal: a new review re-extracts the requirements from scratch and, given the stochastic nature of AI, may produce a different set of requirement IDs that will not line up with your first report. Both options use a credit, so the reason to re-run is a comparable report, not saving a credit.

Yes. A re-run uses one review, the same as a new review. The reason to use 'Re-run with new draft' rather than starting a new review is a like-for-like comparison against the same requirements, not saving a review.

Yes. Every review produces a fully branded, professionally formatted report that you can download as a document and share with your team or client.

Yes. You can upload your company logo and set your corporate colours. These appear on the cover page and throughout the report.

What ReqFit does and doesn't do

No. ReqFit assesses coverage, not prose. It checks whether each requirement has been addressed, not whether your writing is persuasive or eloquent. Writing quality is subjective. Requirement coverage is measurable.

No. ReqFit identifies coverage gaps and compliance issues. It does not predict outcomes, score your commercial competitiveness, or assess how an evaluator will feel about your response. What it does tell you is whether you have addressed every stated requirement, which is the foundation that winning proposals are built on.

No. ReqFit focuses on the technical and written response. It does not evaluate your pricing strategy, fee structure, or commercial terms. Pricing decisions depend on market context that falls outside the scope of compliance analysis.

No. Design and layout are subjective. ReqFit focuses exclusively on whether the content of your proposal addresses the requirements in the RFP. A beautifully designed proposal that misses a key requirement will still be flagged.

No. ReqFit reviews. It does not write. You keep full control of your content. The report tells you what needs attention so you can decide how to address it. This is a deliberate design choice. The goal is to support your judgement, not replace it.

No. ReqFit handles the structured compliance review that a bid manager would typically do manually. It does not replace strategic advice, win theme development, or the experience of someone who knows your client. Think of it as a tool that frees your most experienced people to focus on strategy rather than checking requirements off a list.

Pricing and billing

Yes. If you have a subscription and run out of reviews mid-cycle, you can top up with a one-off single review or a one-off pack at any time. Your subscription continues unchanged.

Any reviews already applied to your account remain valid until their individual 12-month expiry date. Cancelling stops future reviews being applied. It does not remove reviews you already have. See our refund policy for the full billing terms.

Yes. No watermarks, no reduced analysis, no restricted features. The output is identical. We want you to evaluate ReqFit on a live proposal, not a demo version of it.

Single reviews start from £49. Packs of 5 and 10 reviews are available at lower per-review rates. Your first review is free, no credit card required.

All payments are handled by Paddle, a dedicated billing platform used by thousands of SaaS companies worldwide. ReqFit never sees, stores, or touches your payment details. See our refund policy for billing terms and how Paddle handles refunds.

From the ReqFit blog

Our blog covers the practical side of proposals, tenders, and RFPs. The questions below are drawn directly from those articles, with links through to the full piece if you want to read further.

Strategy

Choosing the right opportunities, qualifying decisions, and focusing your resources where they count.

Score the opportunity against a set of qualification criteria before committing resources. The six that matter most are strategic fit, relationship strength, resource availability, sector win history, competitive landscape, and time to produce a quality submission. If more than two criteria score low, the opportunity is probably not worth pursuing.

Read more: Bid or no bid: how to choose the right RFPs

A bid/no-bid framework is a structured scoring method for deciding whether to respond to an RFP. Each criterion is scored on a simple scale, and the total determines whether the opportunity clears a minimum threshold. It replaces gut instinct with a repeatable process that the whole team can apply consistently.

Read more: Bid or no bid: how to choose the right RFPs

There is no universal number. The right volume depends on your team's capacity to produce quality submissions. Most teams would improve their win rate by responding to fewer RFPs and investing more time in each one. If your proposals are consistently average, you are probably bidding on too many opportunities.

Read more: Bid or no bid: how to choose the right RFPs

Yes. The period between deciding to bid and starting to write is valuable. Submit clarification questions early, map the evaluation criteria before drafting, and assemble the right team while there is still time. Then run a compliance check against the RFP before the main writing effort begins to identify gaps early.

Read more: Bid or no bid: how to choose the right RFPs
Fundamentals

Core concepts every proposal professional should understand, from terminology to evaluation mechanics.

One page is the standard for most proposals. For longer, more complex bids (above £500,000 or highly technical submissions), two pages can be justified, but only if every sentence adds information the evaluation panel needs. If in doubt, cut to one page.

Read more: How to write an executive summary that evaluators actually read

No. Pricing belongs in the commercial section of the proposal, where evaluators expect to find it and where it can be assessed alongside the full scope of work. Including it in the executive summary pulls attention to cost before the evaluator has had the opportunity to assess the value you are offering.

Read more: How to write an executive summary that evaluators actually read

Not knowing what the section is actually for. Without a clear sense of purpose, most writers default to what feels safe: an introduction, a capabilities overview, a positive closing. The result looks professional but misses what evaluators are looking for. Start with the client's need, not your credentials.

Read more: How to write an executive summary that evaluators actually read

Last. You cannot accurately summarise a proposal you have not yet written. Writing it first risks creating a version of the proposal that does not reflect what you actually submitted. Plan the structure of your executive summary early, but write the final text after the main document is complete.

Read more: How to write an executive summary that evaluators actually read

In most practical respects, yes. Both are formal documents issued by a buyer asking suppliers to respond to defined requirements. The difference is largely sectoral: tender is the standard term in construction, public sector, and UK procurement, while RFP is more common in technology and professional services.

Read more: RFP, proposal, tender: what's the difference

RFP stands for request for proposal. It is a formal document a buyer issues when they know what problem they want to solve and want suppliers to propose how they would approach it. The buyer sets out requirements and evaluation criteria, and submissions are assessed and scored against those criteria.

Read more: RFP, proposal, tender: what's the difference

An RFP (request for proposal) asks suppliers to propose a solution. An RFI (request for information) is an earlier stage document used to gather market intelligence before a formal process begins. An RFQ (request for quotation) is focused on price rather than approach, typically used when the buyer already knows what they want and is comparing costs.

Read more: RFP, proposal, tender: what's the difference

Usually both, and the distinction matters. A pitch typically involves a presentation with more room for creativity and relationship. An RFP is a structured document with scored criteria that your response must address directly. If the document has numbered requirements and published evaluation weightings, treat it as an RFP regardless of what the covering email calls it.

Read more: RFP, proposal, tender: what's the difference

The most common reason is failing to address one or more stated requirements in the RFP. Evaluators score against specific criteria, and any criterion left unanswered typically receives zero marks, dragging the overall score down regardless of how strong the rest of the proposal is.

Read more: Why proposals fail: the seven gaps that cost you contracts

Yes, and it happens regularly. Evaluators score the document, not the organisation. If your proposal does not clearly communicate your solution against each requirement, the evaluator cannot give you credit for capability that is not demonstrated on the page.

Read more: Why proposals fail: the seven gaps that cost you contracts

Most RFPs contain between 10 and 30 individually scored requirements, depending on the sector and contract value. Public sector tenders and regulated industries tend to have more. The total number is less important than whether every one of them receives a clear, evidenced response.

Read more: Why proposals fail: the seven gaps that cost you contracts

A requirement gap occurs when an RFP states a specific criterion or question and the proposal does not address it at all. This is different from a weak response. A weak response scores low. A requirement gap scores zero, because the evaluator has nothing to assess.

Read more: Why proposals fail: the seven gaps that cost you contracts

It depends on the weighting. If the 30% you cannot meet carries low evaluation weight, a strong response on the remaining 70% can still be competitive. If the missing requirements are heavily weighted or mandatory pass/fail criteria, your chances are poor. The decision should be based on a clear analysis of the scoring model, not a gut feeling.

Read more: Why proposals fail: the seven gaps that cost you contracts
Tactical

Practical techniques for improving specific parts of your proposal process.

General purpose AI tools are not designed with confidential commercial documents in mind. Proposals routinely contain pricing strategy, staffing plans, proprietary methodology, and client intelligence. Before uploading, check the tool's data handling and retention policy carefully. Purpose-built proposal review tools designed for commercial use operate under stricter data handling standards.

Read more: Why a general AI tool cannot review your proposal

A context window is the maximum amount of text an AI model can process in a single session. When a document exceeds this limit, the model cannot consider all of it at once. For long RFPs and detailed proposals, this means parts of the document may be silently dropped from the review without any warning, leading to gaps you would never know about.

Read more: Why a general AI tool cannot review your proposal

Not reliably. General purpose AI tools produce unstructured feedback that varies depending on how the question is phrased and when it is asked. A dedicated proposal review tool applies a consistent framework every time, works requirement by requirement, and produces a structured, comparable output. For one-off informal sense-checking, general AI can be useful. For a repeatable review process, it is not sufficient.

Read more: Why a general AI tool cannot review your proposal

With a general purpose AI tool, you often cannot know. If the combined length of your RFP and proposal exceeds the tool's context window, content will be dropped without notification. Purpose-built proposal review tools are engineered to handle document length as a core design requirement, using multi-pass processing to ensure nothing is silently dropped.

Read more: Why a general AI tool cannot review your proposal

A mid-market proposal typically involves 30-60 hours of combined staff time across writing, review, and coordination. At loaded salary costs of £40-70 per hour, that translates to £1,500-4,000 in people costs per proposal, before accounting for management time or the opportunity cost of diverted capacity.

Read more: The real cost of one missed requirement in a proposal

Industry research consistently reports average RFP win rates of between 20% and 35% for competitive procurement processes. For companies without a dedicated bid function, win rates at the lower end of this range are common. This means most proposals fail, making pre-submission quality checks one of the highest-return investments a bid team can make.

Read more: The real cost of one missed requirement in a proposal

Start with your average contract value and multiply it by your estimated win rate improvement. A team winning £150,000 contracts at a 25% rate that improves to 30% generates an expected £7,500 more per proposal attempt. Compared to the marginal cost of a structured pre-submission review, the return is clear and requires no complex modelling to see.

Read more: The real cost of one missed requirement in a proposal

Submitting blind means sending a proposal without a structured check against the RFP's specific requirements and evaluation criteria. The team believes they have covered everything, but without a systematic comparison, gaps that are clearly present in the brief can go unnoticed until the client scorecard arrives. By then, the opportunity is gone.

Read more: The real cost of one missed requirement in a proposal

The most common errors at submission stage are process failures rather than content failures: missing signatures, wrong file format, appendices not attached, and page limits miscounted. Content gaps should be caught earlier in the review process. By the time you are an hour from the deadline, there is not enough time to fix them properly.

Read more: Why experienced bid managers never submit on deadline day

Yes. Buyers can and do disqualify submissions that do not follow stated formatting requirements, particularly in public sector and highly regulated procurement. Exceeding a page limit, submitting in the wrong file format, or failing to include a mandatory compliance declaration are all grounds for rejection regardless of how strong your content is.

Read more: Why experienced bid managers never submit on deadline day

In an ideal world, your final hour involves very little. The submission should be ready the evening before, so the final check is confirming the file is correctly named, logging into the portal, uploading, and getting confirmation of receipt. If you are making content changes in the final hour, something has gone wrong earlier in the process.

Read more: Why experienced bid managers never submit on deadline day
Guide

Step by step walkthroughs of key proposal activities, from submission to evaluation.

They score each answer against the published criteria for that question, usually on a 0 to 5 or 0 to 10 scale, then apply the weightings and combine the result with the price score. The highest total wins. They mark against the scorecard, not on overall impression.

Read more: The proposal scoring framework: how evaluators actually score your bid

A 3 usually means your answer meets the requirement but stays generic. A 5 means it is specific, tailored to the buyer, and backed by evidence. The biggest single scoring gain is normally moving an answer from generic to specific and evidenced.

Read more: The proposal scoring framework: how evaluators actually score your bid

They read to score, working through each question against its criteria rather than reading cover to cover for a general impression. If your answer to a criterion sits in the wrong section, it can be missed and marked down. Put each answer where it is asked for.

Read more: The proposal scoring framework: how evaluators actually score your bid

After evaluators score independently, they meet to compare and agree a final consensus score for each answer, with the reasons recorded. This moderation step reduces individual bias and creates an audit trail the buyer can defend if the result is challenged.

Read more: The proposal scoring framework: how evaluators actually score your bid

Most formal evaluation panels consist of two to four evaluators. Public sector procurement often requires a minimum of two independent scorers to reduce bias and comply with procurement regulations. Each evaluator scores independently before the panel convenes to moderate and agree a final consensus score.

Read more: What happens to your proposal after you submit it

Timescales vary by procurement size and complexity, but most formal evaluations take between two and six weeks from submission deadline to notification of outcome. Large public sector frameworks can take longer. The RFP or ITT typically states the expected evaluation period in the procurement timetable.

Read more: What happens to your proposal after you submit it

In formal public sector procurement, buyers must publish evaluation criteria and weightings in the procurement documents, but are restricted from sharing scoring guidance privately with individual bidders. In the private sector, clarifying questions during a designated Q&A window are usually permitted. Understanding how to read published criteria accurately is more reliable than seeking additional guidance from the buyer.

Read more: What happens to your proposal after you submit it

Length itself does not affect scoring - evaluators score against criteria, not word count. However, proposals that significantly exceed stated page or word limits may be returned or have excess content discounted. Concise, well-structured responses to each criterion consistently outperform lengthy, discursive ones.

Read more: What happens to your proposal after you submit it
Deep dive

Detailed explorations of proposal challenges for specific roles, sectors, and situations.

AI can produce a grammatically correct, well formatted proposal, but it cannot supply the client knowledge, project evidence, and team experience that evaluators actually score. Without those, the output reads as generic and scores accordingly.

Read more: Why AI-written bids are losing you work

Evaluators score against specific criteria and look for evidence that you understand their situation. AI-generated content tends to be interchangeable, lacking the specificity and proof points that separate a competitive submission from a generic one.

Read more: Why AI-written bids are losing you work

AI works best after a human has drafted with real knowledge. It can tighten language, check consistency, and review coverage against the brief. Using it to generate content from scratch, rather than to review or refine human-written content, is where most teams run into problems.

Read more: Why AI-written bids are losing you work

Even well maintained content libraries have gaps, and AI fills those gaps with generated content rather than flagging them. Unless your library is complete, current, and accurately tagged, the AI output will contain a mix of real and fabricated material that is difficult to distinguish.

Read more: Why AI-written bids are losing you work

No. ReqFit does not generate, draft, or suggest any proposal content. It reviews the document your team has already written against the brief you are responding to, identifying where you have addressed requirements and where gaps remain. The writing is always yours.

Read more: Why AI-written bids are losing you work

Still got questions?

Whether you are evaluating ReqFit for your team, unsure which plan fits your volume, or want to talk through enterprise options, our team is happy to help. No sales scripts, just straight answers.

Get in touch

We typically respond within one business day.

Cookie Policy