Your pipeline notice is a market development tool, not a compliance chore

Time is the barrier, not capability

The reason smaller suppliers lose out is rarely that they cannot deliver the work. It is that they cannot assemble a bid inside a short window while also running the business. Large suppliers keep permanent bid capability. A twenty person firm does not, and every tender it pursues costs it capacity it was using elsewhere.

Advance notice changes what is possible. Twelve months of warning lets a small provider recruit, partner, get accredited, arrange finance and build the evidence base that a public sector bid demands. Two weeks of warning lets it decide not to bother.

That is why the guidance links pipelines to a competitive and diverse market. Publishing forward information does not lower any standards. It removes a timing barrier that filters out capable suppliers before evaluation ever begins.

What most organisations get wrong

The first mistake is publishing the minimum with the minimum detail. A pipeline entry reading professional services, various, next financial year satisfies nobody. A supplier cannot plan against it, so the entry generates no benefit while still costing the effort of publishing.

The second is treating it as a one off. Pipelines are published, and then plans change, and the published version silently becomes wrong. Once a market has planned against a pipeline that turned out to be fiction, the next publication is discounted. Credibility is the asset here and it is easily spent.

The third is not having the internal data. Many organisations genuinely do not know what is coming, because contract end dates live in service area records, extensions get agreed locally, and nobody holds a consolidated forward view. The pipeline exercise then becomes a fire drill of chasing colleagues, which is why it happens as rarely as possible and produces poor results when it does.

The fourth is publishing to the wrong place. The guidance points to the central digital platform and publication of information material for a reason. A pipeline on a page of your own website that suppliers do not know exists is not reaching the market.

What to do about it

Fix the data first. If contract end dates, values and renewal decisions are held centrally, the forward look becomes a report rather than a project, and publishing more often stops being expensive. Most authorities that struggle with pipelines have a data problem wearing a publication problem as a disguise.

Then commit to a cycle and stick to it. Quarterly is enough for most organisations. Publish changes as well as additions, and let entries move or drop off with a visible reason. A pipeline the market can watch evolve is more useful than one that appears perfect and turns out to be stale.

Finally, put in enough detail to be actionable: indicative scope, indicative scale, indicative timing. Suppliers understand that early plans are provisional. What they cannot work with is an entry so general it tells them nothing about whether to prepare. Get that right and the pipeline stops being a return you file and starts being the reason a better field turns up when you go to market.

The takeaways

• The Act requires pipeline notices in certain circumstances, set out in section 93 and regulation 15.
• The guidance frames forward pipelines as one of the most important things authorities can do for the market.
• SMEs and voluntary, community and social enterprises benefit most, because they need lead time to prepare.
• Vague entries and stale pipelines destroy the benefit while keeping the cost.
• Central contract data makes regular, detailed publication cheap enough to sustain.

Want the full breakdown?

The complete explainer covers the key facts, the requirements in detail and a practical action list, free and printable in the Procurement Library.