You've probably got one open right now. A pre qualification questionnaire on one screen, old submissions on another, and a folder full of policies that may or may not still be current.
That's the point where many applicants lose marks before they've written a decent answer. Not because they lack capability. Because they treat the PQQ like admin instead of what it really is. A scoring exercise designed to remove risk from the buyer's shortlist.
Good pre qualification questionnaire answers don't sound polished for the sake of it. They make an evaluator's job easy. They prove compliance, show relevant experience, and remove reasons to exclude you.
What Evaluators Really Look For in a PQQ
A PQQ is a filter first. It is not a place to be clever.
Buyers use it to reduce a large field to a manageable shortlist. That means your job is simple. Pass the mandatory checks, match the stated criteria, and look like a low-risk supplier. If you miss any one of those, strong delivery capability won't save you.
Read the documents like an evaluator
A common approach involves reading the questionnaire line by line and immediately beginning to draft. That's too late. Start with the evaluation method.
Look for:
- Mandatory fail points such as missing insurance evidence, incomplete declarations, unsupported financial information, or unanswered pass/fail questions.
- Scored sections where you need more than compliance. This is usually where experience, method, governance, and policies are compared.
- Buyer priorities hidden in repeated wording. If “occupied environment”, “social value”, or “programme certainty” appears across documents, that priority will shape how your answers are read.
A lot of poor submissions fail because they rely on old generic content. That is a direct scoring problem, not a style issue. Failure to align with a buyer's specific evaluation criteria results in disqualification rates approaching 25% for SMEs attempting to use uncustomised submissions, according to Thornton & Lowe's guidance on PQQs.
Practical rule: If the buyer has used different wording, they usually want a different answer.
Separate compliance from persuasion
Treat the questionnaire in two layers.
The first layer is compliance. That means dates, attachments, signatures, insurance, policies, account information, certifications, and declarations all match exactly.
The second layer is persuasion. That's where you show relevance. Not broad competence. Relevant competence for this contract, this sector, this risk profile, and this delivery environment.
A simple review table helps:
| Question type | What the evaluator is checking | What strong answers do |
|---|---|---|
| Pass/fail | Can we keep this supplier in the process? | Give exact evidence and attachments |
| Financial | Are they stable enough for this contract? | Match the requested documents and explain anomalies clearly |
| Technical | Have they done similar work? | Use directly comparable projects |
| Policy and governance | Do they manage risk properly? | Show current, implemented policies rather than vague statements |
Think shortlist, not showcase
A lot of suppliers try to prove everything they've ever done. That usually weakens the answer.
Evaluators aren't looking for your whole story. They're looking for confirmation that you meet the threshold and won't create problems later. If you want a useful habit, ask this after every draft sentence: would an assessor score this, or just skim past it?
This is also where good tender monitoring matters. If you've spotted the opportunity early, you've got time to check document requirements properly, assign owners, and avoid the last-day rush. A tool built for bid teams, such as Bidwell for bid managers, helps keep the pack organised before the writing starts.
Build Your Evidence Library Before You Write a Word
Most lost time in PQQ work has nothing to do with writing. It goes on chasing evidence.
Someone needs the latest insurance certificate. Finance needs to confirm which accounts were filed. Operations needs to find case studies. Then you discover the H&S policy in the shared drive isn't the current one. That's how a routine submission turns into a scramble.
Build one source of truth
Your evidence library should hold approved content and the supporting files behind it. Not just final answers.
Include:
- Financial records such as filed accounts, turnover figures, profit and loss statements, and balance sheets.
- Insurance documents including public liability and professional indemnity where relevant.
- Core policies like Health & Safety, environmental, quality, equality, and modern slavery.
- Accreditations and certificates for ISO standards, SSIP, CHAS, training records, and trade memberships.
- Project evidence with short case studies, client references, contract values if you're allowed to disclose them, and lessons learned.
The financial piece catches a lot of suppliers out because they assume one set of summary figures will do. In practice, most UK pre-qualification questionnaires explicitly require suppliers to submit two or three years of filed company accounts, including turnover figures, profit and loss statements, and balance sheets, as a mandatory threshold for financial standing, as outlined in Tender Consultants' overview of pre-qualification questionnaires.
Organise for retrieval, not storage
Folders alone won't save you. The structure matters.
Use a naming convention that lets anyone find the right file fast. Include document type, business unit if needed, issue date, renewal date, and approval status. If you work across entities, separate them clearly. A surprising number of submissions go out with the wrong company document attached.
Keep two versions of core answer content. An approved master version, and a live working version for adaptation.
A practical layout might look like this:
- Corporate for registrations, policies, org charts, declarations
- Finance for accounts, statements, forecasts, credit notes
- Insurance for certificates and schedules
- People for CVs, training, qualifications
- Projects for case studies and references
- Accreditations for ISO, SSIP, sector-specific approvals
Use the library as a working asset
The best evidence libraries aren't passive archives. They shape faster, cleaner answers because the team already knows what approved wording and proof exists.
That's where a knowledge base earns its keep. If your team stores approved answers, supporting documents, and reusable case studies in one place, drafting becomes a review task rather than a hunt. If you want examples of how teams structure this, Bidwell's guides are useful for setting up a repeatable process.
How to Structure High Scoring PQQ Answers
Weak PQQ answers are usually not wrong. They're just hard to score.
They ramble. They make claims without proof. They answer the topic but miss the actual wording of the question. That forces the evaluator to do interpretation work, and that never helps you.
Use a structure that forces evidence
For technical and policy questions, I tend to use STAR or CBAR.
- STAR works well for examples. Situation, Task, Action, Result.
- CBAR works well for method and improvement. Context, Baseline, Action, Result.
Either framework stops you drifting into generic corporate language. It gives the assessor four things they can recognise quickly: where, why, what you did, and what changed.
Completing a PQQ from scratch can take 20 to 40 hours for a company new to public sector bidding, according to Bidwell's explanation of the PQQ process. That's exactly why structure matters. If every answer has to be invented each time, you burn hours and still end up with inconsistent quality.
Weak answer versus strong answer
Take a common question: Describe your approach to quality management.
Weak answer
We are committed to quality and take a proactive approach across all our projects. Our experienced team follows strict internal procedures to ensure a high standard of delivery. We review performance regularly and work closely with clients to maintain satisfaction.
Nothing there is false. None of it is especially useful either.
Stronger answer using CBAR
Context: We apply our quality management system across mobilisation, delivery, inspection, handover, and post-project review.
Baseline: For contracts of this type, the buyer's main quality risks are usually incomplete records, inconsistent site standards, and late identification of defects.
Action: We control these risks through documented inspection and test processes, defined sign-off responsibilities, non-conformance reporting, corrective action tracking, and regular internal review against our quality procedures. Project leads are responsible for maintaining evidence, and any issue affecting compliance is escalated through a named manager.
Result: This approach gives the client a clear audit trail, earlier issue detection, and consistent quality records from start to finish.
That version is easier to score because it mirrors buyer risk. It doesn't just say you care about quality. It shows how quality is controlled.
Make your answers easy to mark
Good structure is also document design. Assessors read fast.
Use:
- Short opening lines that answer the question directly.
- Headings or bold labels when the portal allows formatting.
- Bullets for evidence rather than burying it in prose.
- Buyer language taken from the specification and contract notice.
- Comparable examples instead of a general capability statement.
If your internal content is messy, fix that first. Teams that improve their answer libraries usually improve their underlying documentation too. This makes optimizing technical documentation relevant. The same habits that make operational documents usable also make tender responses clearer and easier to trust.
The best answer often feels slightly plain. That's because it's written for scoring, not applause.
If you use AI for drafting, this structure matters even more. A response generator can only produce usable first drafts if your knowledge base contains current evidence and your prompts reflect the buyer's actual criteria. One practical example is Bidwell's PQQ workflow, which uploads the questionnaire, checks your stored content, and drafts responses around the evidence you already hold.
Common PQQ Questions with Example Answers
Most PQQs ask the same core things in slightly different wording. Financial standing. Health and safety. Environmental management. Quality assurance. Relevant experience.
The mistake is copying a stock paragraph into each one. Buyers don't score topics. They score whether your answer meets their requirement.
For larger public construction projects, the benchmark is now clearer. The Common Assessment Standard requires suppliers to prove compliance across financial stability, Health & Safety (SSIP), Environmental management (ISO 14001), and Quality assurance (ISO 9001), as set out on Constructionline's Common Assessment Standard page.
Financial stability
A weak answer says you are financially secure.
A better answer states what you've provided and addresses any obvious concern.
Example answer
We have provided the requested filed accounts and supporting financial information for the period specified in the questionnaire. These documents evidence our trading history and financial standing. Where any figure requires context, such as a one-off cost or group structure issue, we have explained it clearly in the financial notes so the buyer can assess the position accurately.
Why this works: it points the evaluator to evidence and deals with anomalies before they become doubts.
Health and safety
Buyers want to know whether your H&S system exists in practice, not just on paper.
Example answer
Our Health & Safety management arrangements are led by named responsible personnel and supported by current policies, training records, risk assessment procedures, and incident reporting processes. We have provided evidence of our current SSIP-related compliance where requested, alongside the relevant policy and insurance documents. Project-specific controls are reviewed before mobilisation and updated where site conditions or delivery risks change.
Why this works: it shows ownership, process, and current evidence.
Environmental management and quality assurance
These answers should show controlled systems rather than broad intentions.
| Topic | Weak line | Better line |
|---|---|---|
| Environmental | We care about sustainability | We manage environmental impacts through documented procedures, defined responsibilities, and evidence of review under our environmental management system |
| Quality | We always deliver high standards | We control quality through planned inspections, documented records, corrective actions, and management review under our quality procedures |
Relevant experience and case studies
Here, many otherwise compliant submissions lose ground. The buyer isn't asking for your favourite project. They want the closest match.
Use case studies that mirror:
- Sector such as education, housing, healthcare, highways
- Scale in complexity and delivery environment
- Type of works rather than broad service category
- Constraints such as live sites, stakeholder management, compliance demands
A useful case study pattern is simple:
- Project context
- Client challenge
- Your actions
- Outcome and learning
Don't pick the biggest contract if it isn't the closest fit. Pick the one that makes the evaluator think, “Yes, they've done this before.”
PQQ Pitfalls That Get You Disqualified
A lot of teams think disqualification comes from major failures. Often it comes from ordinary sloppiness.
The policy is out of date. The case study is impressive but irrelevant. A question asks for an explanation and gets “N/A”. A declaration is attached but not completed correctly. None of that feels dramatic when you're drafting. It looks serious when an assessor is checking risk.
The copy and paste trap
Reused content is fine if it's adapted properly. Most of the time it isn't.
You can usually spot a pasted answer in seconds. It uses the wrong client language, references the wrong service line, or answers a broader question than the one asked. Evaluators spot that too. It tells them your submission wasn't prepared carefully.
The same applies to unsupported “N/A” answers. If the buyer asks for something you don't hold, explain why, state the nearest equivalent evidence, and show how the requirement is otherwise managed. Silence looks evasive.
Currency matters more than people think
PQQs are not static documents. Buyers use them to assess current risk.
That's why stale evidence hurts. Suppliers who neglect to update their PQQ information annually face a 50% reduction in credibility scores for health and safety policies and insurance certifications, while those who use a 'lessons learned' methodology in answers see a 2.5x higher rate of progressing to the next stage, based on the material linked with Annex A core PQQ questions.
A quick red-flag checklist
Before submission, check these hard:
- Dates: Insurance, policy review dates, accounts, certificates, and declarations all need to be current.
- Entity accuracy: Make sure the legal entity on the form matches the legal entity on the attachments.
- Case study fit: Use examples that match the contract, not just your most prestigious work.
- Lessons learned: Show what improved, not only what happened.
- Attachments: Name them clearly and confirm they open.
If an assessor has to guess whether you comply, you've already made the answer weaker than it needed to be.
Your PQQ Questions Answered
The terminology has changed, the rules are shifting, and a lot of old guidance is already dated. These are the questions that come up most often when teams are trying to keep their pre qualification questionnaire answers current.
What's changing with PSQs
The biggest practical issue is that old PQQ habits don't always map neatly to the newer process.
According to Bidscript's guide to PSQs, 68% of UK SMEs failed their first PSQ attempt in 2025 due to incomplete disclosures and outdated certifications. That matters because many legacy answer banks were built around older PQQ or SQ wording, not the tighter disclosure and matching requirements now appearing in PSQs.
If you're updating your library, review director-level declarations, exclusion grounds, and contract examples. A strong example that doesn't match sector, scale, or contract type can still weaken your position.
What if you're a newer company
This comes up a lot. You may not have the trading history a buyer would prefer.
That doesn't mean you should guess, pad, or hide gaps. State your position clearly. Provide the exact financial material you do have. If the questionnaire allows explanation, use it to show governance, backing, cash control, relevant leadership experience, and any directly comparable delivery credentials.
Buyers can work with honest explanation more easily than vague claims. What they won't like is inconsistency between your form, attachments, and declarations.
What's the difference between a PQQ, SQ, ITT and CAS
They're related, but they're not the same thing.
- PQQ usually refers to the pre-qualification stage where the buyer checks whether you should be shortlisted.
- SQ is the Selection Questionnaire terminology used in many public procurement processes for that same early-stage filtering role.
- ITT is the Invitation to Tender. That's the full bid stage where pricing, methodology, mobilisation, and delivery proposals are assessed in depth.
- CAS is not a tender stage. It's a pre-qualification standard used in construction, particularly relevant on larger public projects.
A useful way to think about it is this: PQQ or SQ gets you through the door. ITT decides who gets the contract. CAS can serve as the recognised evidence standard in the background, depending on the project.
Should you still use old answer templates
Only as raw material.
Templates are fine for holding approved base content. They're poor substitutes for live responses. Every submission should be checked against current wording, current documents, and current regulation. If your team still uses answer banks built around PAS 91 language, review them carefully before reusing them.
Old templates save time only if someone has already done the hard work of updating them.
How do you make the process faster without making answers generic
Use a repeatable workflow.
Monitor opportunities early. Keep your evidence library current. Store approved answer content with the documents behind it. Draft from structured case studies rather than from memory. Then review against the buyer's criteria line by line.
That's the essential trade-off. Speed helps only when it protects relevance and compliance.
If you want one system for tender monitoring, a central knowledge base, and AI response generation for public sector bids, Bidwell is built for that workflow. It helps teams spot relevant opportunities, store approved evidence and case studies, and draft specific responses for questionnaires without starting from a blank page every time.
