Write bids that score higher. Every time.

How does the bid writing module work?

It structures your response around the evaluation criteria for each specific tender - not just the questions asked. Criteria, weightings and scoring methodology analysed before you start writing.

Does it use our existing case studies?

Yes. Your knowledge base - case studies, CVs, method statements - is stored and reused across bids. Content is quality-controlled and version-managed.

Can it improve our social value score?

Yes. The social value module builds responses around TOMS and NCVO frameworks with commitments structured to be measurable and credible.

Start with the criteria, not the question

Before you write a word, extract the award criteria, the weightings and the scoring matrix into a single sheet. You are looking for three things: how many marks each question carries, what the rubric says a top score looks like, and whether any question is pass or fail. A question worth five per cent does not deserve the same effort as one worth thirty, and suppliers routinely spend their best writing on the wrong answer because they worked through the document in page order.

Once you have the weightings, read the rubric language closely. A descriptor that rewards a response that is comprehensive, fully evidenced and demonstrates deliverability is telling you exactly what the evaluator has to be able to tick. Scoring descriptors are not decoration. They are the checklist your answer will be marked against, and the phrases they use should appear, honestly and in context, in what you write.

Then build a response plan per question before drafting. Note the marks, the word limit, the sub questions, the evidence you will cite and the person who owns the content. Ten minutes of planning per question removes most of the rework later, and it exposes early where you have no evidence at all, which is the point at which a bid or no bid decision can still be revisited cheaply.

• Weighting and available marks for every question
• Full scoring descriptors, not just the maximum score wording
• Any pass or fail gates and minimum score thresholds
• Word or page limits, and whether appendices are permitted
• Named owner and evidence source for each response

Mirror the question structure in your answer

Evaluators mark under time pressure, often with several bids to score in a sitting. If your answer forces them to hunt for the part that addresses sub question three, you will lose marks you have technically earned. The fix is unglamorous: use subheadings that repeat the buyer's own wording, answer the parts in the order they were asked, and make each part visibly complete before moving on.

Use the buyer's terminology throughout. If the specification says service user, do not write customer. If it refers to mobilisation, do not call it onboarding. This is not flattery, it is traceability: the evaluator is matching your text to their document, and consistent language makes that match obvious. It also reduces the risk of a moderator concluding that you have answered a different question from the one asked.

Front load each section. Open with a direct statement of what you will do, then the detail, then the evidence that it works. Evaluators form a view early, and a response that spends its opening ninety words on company history has spent its most valuable space on content that carries no marks.

Assertion versus evidence

The single most common reason a good supplier scores badly is that the response asserts quality rather than evidencing it. We have extensive experience, we are committed to excellent service and our team is highly skilled are all unscoreable. There is nothing for the evaluator to point at when they write their rationale, and a rationale that cannot be written is a score that will not be awarded.

Evidence has a recognisable shape. It names things: a method, a system, a role, a frequency, a timescale, a measurable outcome, and where possible a comparable contract where the approach has already been used. Compare we respond quickly to faults with faults reported as priority one are attended on site within four hours, monitored through our service desk and reported monthly against the contract KPI. The second is scoreable. The first is noise.

Where you cite a comparable contract, keep it relevant and proportionate. Two or three sentences describing a similar scope, a similar scale and the outcome achieved will do more than a page of unrelated credentials. Be accurate about what you can claim, particularly where work was delivered as a subcontractor or as part of a consortium, because a misstated reference is a compliance problem rather than a scoring one.

Method statements: describe how, not why

A method statement is an operational answer. It should read like an instruction to your own delivery team, edited for an outside reader. Who does what, in what sequence, using what systems, to what standard, checked by whom, escalated how when it goes wrong. Most weak method statements explain why the approach matters. The evaluator already knows why it matters, which is precisely why they asked the question.

Structure helps enormously here. A short narrative followed by a sequenced process, roles and responsibilities, quality controls, and how performance will be measured gives the evaluator four separate places to award marks. Where a diagram or table genuinely compresses information, use it, but check whether it counts towards the word limit and whether the portal preserves formatting.

Be specific about resource. Named roles, indicative headcount, coverage hours, geographic reach and how you flex when demand changes are all details buyers use to test whether the plan is real. A method statement that never mentions a person is usually describing an aspiration, and experienced evaluators recognise the difference immediately.

Mobilisation, transition and risk

Mobilisation questions test whether you have done this before. The answer should be a dated plan running from contract award to steady state service, with the activities that matter to the buyer visible: TUPE where relevant, recruitment and vetting, systems access and data migration, asset and stock handover, policies and training, testing, and the point at which you accept full service responsibility. Give it milestones and name who owns them.

Transition from an incumbent is a specific risk the buyer is anxious about, so address it directly rather than assuming goodwill. Say what you need from the outgoing provider, what you will do if that cooperation does not materialise, and how continuity of service is protected in the meantime. A supplier who has clearly planned for an unhelpful handover is more reassuring than one who assumes a smooth one.

Risk questions are answered badly more often than any other type. A credible answer identifies risks that are specific to this contract, not generic business risks, assesses likelihood and impact, sets out the mitigation, names the owner, and says how the risk is monitored and reviewed through delivery. Include at least one risk that is uncomfortable to admit. A register containing only risks you have obviously already solved reads as a marketing document.

• Risks specific to this scope, site, cohort or system
• Likelihood, impact and the residual position after mitigation
• Named owner and the forum where the risk is reviewed
• Contingency and the trigger point at which it is invoked
• How risks are shared or transferred under the contract terms

Social value that can survive contract management

Social value now carries meaningful weight in most public competitions, and buyers are increasingly measuring delivery rather than filing the promise. Commitments should therefore be written as things you can be held to: the activity, the quantity, the timescale, the geography, the beneficiary group and the person accountable. Two apprenticeships recruited from the borough in year one, with names reported quarterly, is scoreable and deliverable. A commitment to supporting local communities is neither.

Proportionality matters. Commitments should be sensible relative to contract value, duration and the size of your delivery team, and evaluators are alert to bids that promise more social value than the margin could possibly fund. Over promising wins a few marks and then creates a contract management problem, a difficult conversation and a performance record that follows you into the next competition.

Tie the commitment to the contract itself wherever you can. Work experience placements linked to the delivery site, local supply chain spend within the service, or carbon reduction achieved through the way this contract is run will always outscore corporate activity that would have happened anyway. Where a buyer uses a measurement model or proxy values, follow their model rather than your own and show the calculation.

Word counts, page limits and appendices

Treat stated limits as absolute. Many buyers state that text beyond the limit will not be evaluated, and portals increasingly enforce it automatically. An answer truncated mid sentence looks careless and loses the conclusion, which is often where the strongest content sits. Write long in draft, then edit down by removing preamble and repetition rather than by cutting evidence.

Check the counting rules before you rely on them. Whether headings, tables, captions and diagrams count varies between buyers, as does whether a page limit assumes a minimum font size and margin. If the instruction is ambiguous, ask through the clarification process and rely on the published answer rather than an assumption that suits you.

Appendices are the most misunderstood part of a bid. Evaluators can normally only score what the instructions permit them to consider, so material pushed into an unrequested appendix is often ignored entirely, and in some cases treated as an attempt to circumvent the word limit. Use appendices for what was asked for: certificates, insurance evidence, accounts, organisation charts, policies. Keep the argument itself inside the answer box.

Clarification questions are a tool, not an admission

Suppliers under use the clarification process, usually because they worry that asking a question signals weakness. Clarifications are anonymised, and the answers are normally published to all bidders, so the real risk is the opposite: failing to ask means competing against a reading of the document that may simply be wrong. Ambiguity in a specification, a volume assumption, a pricing schedule or an evaluation instruction is worth resolving in writing.

Ask early and ask precisely. Late questions may not be answered, and a vague question invites a vague answer. Reference the document, the section and the specific wording, then set out the two readings you are choosing between. Keep every published clarification with the bid file, because the answers form part of the tender documents and can change what a compliant response looks like.

Read the clarification log even when you have not asked anything. Other bidders will surface issues you missed, and the buyer's answers often reveal how strictly they intend to evaluate, what evidence they expect and where their real priorities sit.

Dynamic Markets: apply once, stay eligible

The Procurement Act replaced the Dynamic Purchasing System with Dynamic Markets, and replaced utilities qualification systems with utilities dynamic markets. For a supplier the practical consequence is significant. A Dynamic Market is permanently open, so there is no window to miss, and membership cannot be capped, so you are not competing for a limited number of places. Applications must be assessed within a reasonable time, and where your application is pending while a competition is running, it must be considered before that competition concludes.

That changes how you should write a membership application. It is a qualification document, not a tender. Its job is to demonstrate that you meet the published conditions for membership in the categories you want: legal standing, financial standing, insurance, relevant experience, accreditations, policies and any technical capability the market specifies. Write it once, write it properly, and maintain it. Expired insurance certificates and lapsed accreditations are among the most common and most avoidable reasons a member is excluded from a call off.

Do not recycle a membership application into a tender response, or the reverse. Membership evidences capability in general. A call off competition asks how you will deliver a specific requirement, and is scored on that. What you can reuse is the underlying evidence library: policies, case examples, KPI data, staffing models and social value delivery records. Keep that library current and each individual response becomes a shorter, sharper writing job.

Fees differ by sector. Utilities in water, energy and transport may charge suppliers membership and award fees and may run member only tenders. General contracting authorities may not charge membership fees, so if a council or an NHS body asks you to pay to join, ask for the basis of the charge.

Internal review before you submit

Build a review that mimics evaluation. Give a colleague who did not write the bid the question, the word limit and the scoring rubric, and ask them to award a mark and write the rationale. If they cannot write a rationale, the evaluator will not be able to either. This single exercise catches more lost marks than any amount of proofreading, because it tests scoreability rather than style.

Run a separate compliance check against the instructions to bidders: every question answered, every mandatory document attached in the required format, signatures and declarations complete, pricing schedule submitted exactly as issued, and the submission uploaded well before the deadline. Portals slow down in the final hour, and a late submission is almost always fatal regardless of quality.

Finally, capture what you learn. Record the questions asked, the scores received and the feedback given, so the next bid to the same buyer starts from evidence rather than from a blank page. Where writing capacity rather than capability is the constraint, our sister product BidWriter offers AI assisted bid writing built around UK public sector question types, and WinAContract provides free UK tender search if you are still building the pipeline that feeds all of this.