Bid management software that helps you win more.

Bid management and bid writing are different jobs

Bid writing is the craft of producing an answer that an evaluator can score. Bid management is the operational system that decides which opportunities you pursue, who does what by when, what evidence is attached, who reviews it, and how it gets submitted without incident. The two overlap, but they fail in different ways and they need different tools. A brilliant answer submitted late scores zero, and a flawless process around thin content wins nothing.

In practice most suppliers over invest in writing and under invest in management. They buy or build a library of words, then run every bid as an improvised project in email, shared drives and a wall calendar. The symptoms are recognisable: nobody is sure which version is current, two people rewrite the same answer, the insurance certificate attached is last year's, and the final compliance check happens at eleven at night on the day of submission.

The management layer is also where scale lives. One bid can be run on adrenaline. Six concurrent bids with shared subject matter experts and overlapping deadlines cannot. If your win rate holds but your bid volume has stopped growing, the constraint is coordination rather than writing capacity.

Capture and qualification: the gate that saves the most money

Capture begins before a tender notice exists. Under the Procurement Act 2023, which came into force on 24 February 2025, buyers publish more of their intent earlier, through pipeline notices and preliminary market engagement. A capture record should open at that point, holding what you know about the requirement, the buyer, the likely incumbent, the budget signals and the relationships you already have. By the time the notice lands you should be confirming a decision, not starting one.

Qualification then needs to be a scored gate, not a conversation. Bid or no bid decisions made on enthusiasm are the single most expensive habit in the sector, because the cost is paid in the time of the people who also deliver the work. Score fit, evidence, incumbency, commercial viability, capacity and win themes, weight them, set a threshold and hold to it. Record the reasons, including for the bids you decline, because the pattern of your no bids is management information.

Win themes belong in qualification rather than in drafting. If you cannot state, in two or three sentences, why this buyer should choose you over the likely incumbent, you do not yet have a bid worth writing. Capacity deserves the same honesty: who will actually write, review and price the response, against everything else committed in the same fortnight?

Free tender search makes the capture side cheap to run. WinAContract at winacontract.co.uk provides UK tender search at no cost, which is enough to build a structured watchlist by category, buyer and geography that feeds your qualification gate rather than an inbox nobody reads.

• Fit: does this sit inside the categories where we genuinely compete?
• Evidence: can we meet every condition of participation today, with documents?
• Incumbency: who holds it now, and what signals suggest the buyer might change?
• Commercials: is our price credible at the likely budget without eroding margin?
• Capacity: do we have the writers, reviewers and pricing input in this window?
• Win themes: can we state in three sentences why we should win?

Pipeline and portfolio management

A single bid is a project. A set of bids is a portfolio, and it needs to be managed as one. Portfolio visibility means seeing every live opportunity with its stage, value, submission date, owner and probability in one view, so that clashes are visible weeks ahead rather than discovered on the day two responses need the same technical lead. Weighted pipeline value then gives a forecast that operations and finance can plan against.

Stages should reflect how public procurement actually runs: identified, qualified, selection stage, invitation to tender, submitted, standstill, awarded or unsuccessful. Each stage has different work, different owners and different information needs. Tracking them separately also tells you where you lose, which is usually more useful than a single overall win rate. Losing consistently at selection is a very different problem from losing consistently at final scoring.

Portfolio visibility is also how you protect quality. If the calendar shows four submissions inside ten days and two of them are marginal on fit, decline the marginal ones and put the effort behind the strong ones.

Deadline and milestone control

Public sector timetables contain more deadlines than the submission date, and the earlier ones are the ones people miss. Clarification question windows typically close well before the tender does, and once closed you have no route to resolve an ambiguity in the specification. Site visits, supplier days, selection stage returns, portal registration and document downloads all carry their own dates, and portals often cut off at an awkward hour such as midday rather than end of day.

Good practice is to work backwards from the submission time and build internal milestones with real slack: content complete, review complete, pricing signed off, documents assembled, uploaded. The upload milestone should sit at least a full working day before the portal closes. Portal congestion, large file uploads, multi factor authentication failures and expired user accounts are common in the final hours, and buyers are rarely able to accept a late submission even when they sympathise.

After award, the timetable continues. A standstill period runs between the award decision and entering into the contract, and it is the window in which you request and analyse feedback, or raise a concern about a procedural breach. Diarise it. Most suppliers let standstill pass in silence and then wonder, months later, why they lost.

• Clarification window opens and closes
• Selection stage or conditions of participation return
• Site visits, supplier engagement sessions and buyer presentations
• Internal content, review, pricing and assembly milestones
• Portal upload target, set at least one working day early
• Submission cut off time, including the portal's time zone and exact hour
• Standstill period and feedback request

Team coordination, roles and content ownership

Bids fail at the seams between people. The fix is unambiguous ownership at the level of the individual question, not the document. Each question needs a named author, a named reviewer, a named approver for anything commercially or legally binding, and a due date that is earlier than the one you think you need. Subject matter experts should be asked for evidence and facts, not for polished prose, because asking a busy engineer to write persuasively usually produces neither.

Version control matters more than most teams admit. Where responses live in shared documents with concurrent editing, agree who owns the master and when it is locked. Where they live in a bid management system, the version history and the audit trail do that work for you, which also protects you if a claim in the submission is later questioned. Either way, the rule is that only one version is submittable and everyone knows which it is.

Coordination extends outside your organisation. Consortium partners and subcontractors need the same deadlines, templates and evidence standards, and they need them earlier because you have no line management over them.

The content and answer library

A content library is the asset that makes the second, tenth and fiftieth bid cheaper than the first. It holds reusable material in reviewable pieces: method statements, quality and environmental policies, insurance certificates, accreditations, financial statements, personnel CVs, case evidence, social value commitments and standard commercial terms. Each item needs an owner, a review date and a status, so that an expired certificate is visible as a problem before someone attaches it to a submission.

The library should hold components, not finished answers. Reusing an entire previous response without retargeting is one of the most reliable ways to lose marks, because evaluators quickly spot content aimed at another sector, another scoring rubric or, occasionally, another buyer. Reuse the evidence, the numbers and the accredited facts. Rewrite the framing, the emphasis and the structure for the question in front of you.

Tagging is what turns a folder into a library. Tag by question type, sector, buyer, contract value band and evidence type, so that assembling a first draft is a search rather than an archaeology exercise. Keep a canonical version of every recurring fact, such as employee numbers, certification numbers and turnover, in one place. Inconsistent figures across a submission are noticed.

Where AI drafting is used on top of the library, the discipline is the same. BidWriter at bid.winacontract.co.uk provides AI assisted bid writing for UK public sector responses. It should shape and tighten your evidence, never invent facts about your business, because unverifiable claims score badly and can amount to a false declaration.

Review gates and the final compliance check

Reviews should be scheduled gates with defined purposes, not a general request to read the document. A storyboard review, held early, checks that each answer plan addresses the question components, carries the intended win themes and cites specific evidence, before anyone has written prose worth defending. Reviewing at plan stage is far cheaper than reviewing at draft stage, and it prevents the polite reluctance to rewrite work that already looks finished.

Colour reviews are the established discipline for the later stages. A first review checks the draft against the scoring descriptors and asks whether the top band is easy to award. A second checks readability, consistency of tone across authors, and whether the evidence is explicit rather than implied. A final review checks the assembled submission as a whole, including pricing coherence, before sign off.

The compliance check is separate and it is not a proofread. It is a mechanical verification against the tender documents: every required question answered, word and page counts within limits, correct templates used, correct file formats and naming conventions, mandatory attachments present, declarations completed and signed by someone authorised to sign, and pricing entered exactly as the schedule demands. Give it to someone who did not write the bid.

• Storyboard review: does the plan answer the question and carry the win themes?
• Draft review against the scoring descriptors, band by band
• Editorial review for one voice, evidence visibility and readability
• Commercial and legal sign off on anything binding
• Independent compliance check against the instructions to tenderers

Submission mechanics and how bids die at the portal

Every buyer portal behaves slightly differently, and the differences are exactly where submissions fail. Some require each answer typed into a form with a character limit that counts spaces differently from your word processor. Some accept attachments only in specified formats and reject anything else silently. Some require every document to be uploaded and then a separate final action to submit, which is the step people forget, leaving a full response sitting unsubmitted in draft.

The recurring failure modes are boringly consistent: uploading after the cut off time, using the wrong file format or an unaccepted file name, exceeding a word or character count so that the answer is truncated mid argument, missing a signature or an authorised signatory, omitting a mandatory attachment, and entering pricing in the wrong units. None of these are judgement calls. All of them are preventable with a checklist, a rehearsal upload and an early submission.

Register on the portal at the start, not the end. Account approval can take days, permissions may need setting by an administrator, and multi factor authentication tied to a departed employee's phone is a recurring cause of missed deadlines. Keep a record of which portals you are registered on and review it quarterly.

Post award feedback, debriefs and analytics

The Procurement Act 2023 improved what unsuccessful bidders receive. Assessment summaries give more structured information about how your tender was scored than the informal feedback habits of the previous regime often produced. Capture it in a form you can analyse: the score per question, the evaluator commentary, the winning score where disclosed, and your own read of whether you lost on price, on a specific answer or on an interpretation you can address.

Feedback is only useful if it changes something. Route each point back to the library item it affects, update the content, and record the change. Buyers repeat their habits and often reuse evaluation teams and question sets, so a lesson from one competition is frequently worth marks in the next one with the same organisation. Suppliers who skip this resubmit the same weak answer for years without knowing it.

Analytics turn individual outcomes into strategy. Track win rate by buyer, by sector, by value band, by route to market and by whether you were incumbent. Track cost to bid alongside it. The pattern usually shows that a narrow set of buyer types and contract sizes carries almost all your wins, which is the evidence you need to decline the opportunities that feel attractive but historically never convert.

Why the Procurement Act makes bid management continuous

The Act replaced the Dynamic Purchasing System with Dynamic Markets, and replaced utilities qualification systems with utilities dynamic markets. Dynamic Markets are permanently open, membership cannot be capped, applications must be assessed within a reasonable time, and a pending application must be considered before a competition concludes. There is no window to miss, which changes the rhythm of supplier bid management from campaign based to continuous.

That has practical consequences. Membership applications and their supporting evidence become a standing workload rather than an annual scramble, and keeping insurances, accreditations and financial information current inside each market is now a maintenance task with real commercial value. An expired certificate on a market record can remove you from call off competitions you never even see. Fees differ by sector: utilities in water, energy and transport may charge membership and award fees and may run member only tenders, while general contracting authorities may not charge membership fees.

Frameworks work differently again. Purchases under a framework are made as call off contracts, and further competitions often run on short timescales because qualification is already done. Being ready to respond quickly, with a current library and clear ownership, is worth more than any single polished document.

On the buying side, eSourcing Data provides the source to contract platform public bodies use to run this process: sourcing and tendering, supplier onboarding and assurance, evaluation and moderation, contract management, governance and audit, analytics and reporting, and below threshold workflows, with UK data residency and GDPR compliance. Our software is available to public buyers through RM1557.15 G-Cloud 15, with 28 software services listed on the Digital Marketplace plus cloud support services. For suppliers, understanding how the buyer side records, moderates and audits a decision is the clearest guide to what your submission needs to survive.