As the new financial year approaches, one Procurement Act 2023 obligation deserves much more attention from local authorities than it often gets in day to day discussion: the Pipeline Notice.
For councils that expect to pay more than £100 million under relevant contracts in the coming financial year, this is not an optional planning exercise or a helpful market engagement extra. It is a legal requirement, and the deadline comes around quickly. The notice must be published within 56 days of the start of the financial year, which means by 26 May 2026 for the 2026 to 2027 year.
For many local authorities, the challenge is not understanding the rule in principle. It is working out, in time, whether the authority is in scope, what should be included, and who across procurement, finance and commissioning owns the process.
Why this matters right now
The Pipeline Notice is designed to give the market early visibility of future public contract opportunities. Under the Act, it covers intended public contracts with an estimated value of more than £2 million where the authority intends to publish a tender notice or transparency notice during the reporting period.
That reporting period is 18 months, beginning on the first day of the financial year in which the notice is published. In practice, that means authorities need to look beyond their immediate procurement timetable and take a broader view of planned activity.
For local authorities, this is important for two reasons. First, the duty itself may apply. Second, even where it does not, the Pipeline Notice is becoming a practical indicator of procurement maturity, forward planning and market transparency.
Councils that leave this until late April may find that the real problem is not publication. It is the internal coordination needed to identify the right procurements and validate whether the £100 million threshold is met.
Which councils are likely to be in scope
The legal trigger is whether the authority considers that it will pay more than £100 million under relevant contracts in the coming financial year.
That is a broader test than some officers initially assume. It is not limited to new procurements. It is based on payments due in the year under relevant contracts, including existing contracts and future contracts. It also includes below-threshold contracts and contracts awarded under frameworks and dynamic markets.
For larger county councils, combined authorities, metropolitan councils, unitary authorities and other high-spend bodies, that threshold may be reached more easily than expected once existing contractual commitments are included. Authorities should not assume the rule only affects central government or national buying bodies.
Equally, officers should be careful not to over-simplify the calculation. The framework itself is not counted by reference to a notional total framework value where no payments are made under the framework itself. What matters is the value of the relevant contracts awarded under it and the payments expected under those contracts.
What actually needs to be published
A Pipeline Notice is not a single vague statement about future intentions. It is a set of procurement-specific entries covering individual planned procurements over the £2 million threshold.
Although the legal concept is a single pipeline notice, in operational terms authorities are expected to publish details for each procurement separately so that later notices can be linked back properly through the digital system. Those procurements are then presented together as the authority’s pipeline view.
That matters because this is not just about visibility. It is also about data continuity across the procurement lifecycle. The next notice, whether that is a preliminary market engagement notice, a planned procurement notice, a tender notice or a transparency notice, should link back to the originating pipeline entry.
For councils using e-procurement platforms or eSenders, this is one more reason to check local system arrangements early rather than assume publication will sort itself out later.
Why this is more than a compliance exercise
There is a tendency to treat Pipeline Notices as an administrative publication issue. That misses the point.
For local authorities, a credible pipeline can improve supplier engagement, support SME and VCSE readiness, and reduce the stop-start pattern that often weakens competition. It also gives internal teams a clearer basis for planning resource, legal support, governance routes and market engagement activity.
In other words, the Pipeline Notice is one of the clearest places where procurement reform meets practical commissioning discipline. If an authority cannot identify its likely £2 million plus opportunities over the next 18 months, that tells you something important about internal planning maturity.
This is particularly relevant in local government where major procurements may sit across adult social care, children’s services, housing, construction, highways, ICT, waste, transport and professional services, often with different lead officers and different levels of commercial capability.
Common mistakes councils should avoid
One common mistake is assuming the authority is out of scope because the procurement team alone does not control £100 million of annual spend. The legal test is not procurement team budget ownership. It is whether the authority expects to pay more than £100 million under relevant contracts in the year.
Another is treating the exercise as solely procurement-owned. Procurement will usually coordinate, but finance, commissioning, capital programme leads and service departments all hold pieces of the picture. Without those inputs, the pipeline is likely to be incomplete.
A third mistake is assuming the notice must be perfect and final. The legislation requires publication within the 56-day window, but guidance also encourages authorities to review and update the pipeline during the year. That does not remove the need for a serious initial exercise, but it does mean councils should not delay publication simply because some details may still evolve.
A fourth is forgetting that publication is about intended procurements where the authority expects to publish a tender notice or transparency notice. Authorities therefore need to think about likely routes to market, not just contract ideas in the abstract.
What local authorities should do now
The immediate task is to identify whether the authority is likely to cross the £100 million threshold in 2026 to 2027. That assessment should include payments under existing contracts, known future contracts, below-threshold contracts and expected call-off activity where relevant.
Authorities that are clearly above the threshold should then begin assembling their list of intended procurements above £2 million for the next 18 months. That means not only procurements expected in the first half of the year, but also those that may commence later and still fall within the reporting period.
Councils should also confirm who will coordinate publication on the central digital platform, how entries will be linked to later notices, and whether their local systems support the process efficiently. If the authority relies on an eSender or procurement portal, this should be checked early.
Just as importantly, governance teams should recognise that the Pipeline Notice may expose gaps between service planning and commercial planning. Where that happens, the right response is not to treat the notice as a burden, but to use it as a prompt to tighten planning discipline.
The main takeaway
For in-scope local authorities, the 26 May 2026 Pipeline Notice deadline is already close enough to require action now.
The key question is not simply whether a notice has to be published. It is whether the council has a robust enough view of its future contract activity to publish something accurate, credible and useful to the market.
Authorities that start early should be able to manage this well. Authorities that leave it until the last minute may find that the greater risk is not technical publication on Find a Tender, but the absence of a joined-up view of what the council actually intends to buy.