Velstrian Buy

Plan work with the buyer pipeline and contract register

See your upcoming and current contracts in one pipeline, with the publication views public buyers need.

5 min read

What this is for

The buyer pipeline in Velstrian Buy gives a buying organisation one view of its upcoming and current contracts, so planning does not live in a spreadsheet. It works for public and private buyers alike. Public buyers also have publication duties under the Procurement Act 2023, and the pipeline holds the view that supports them, so planning and transparency share one source of truth. A private buyer sees that same view written as a plain forward plan for suppliers.

The views it holds

The pipeline screen shows one job at a time, chosen by a view control, with the pipeline itself as the default. The other views read from the same data. Pipeline notice holds the content a pipeline notice needs (Procurement Act 2023, section 93 (pipeline notices)), and Document packs builds board, committee and business case packs from your own records. The contract register, with its download, sits on the Contracts screen beside the contracts it lists. Because they all read from one place, the planning list and the published views cannot drift apart.

Step by step

  1. Open Velstrian Buy, then Requirements, then its Pipeline tab.
  2. Use the view control near the top to switch between Pipeline, Pipeline notice and Document packs.
  3. Open a row to work on that requirement. A quick request for quotes row opens on the Quick RFQ screen rather than as a full requirement pack.
  4. When you need the contract register for publication or reporting, open Contracts and choose Download contract register.

What happens next

A planned item in the pipeline becomes a requirement you take out to suppliers, then an evaluation, then an awarded contract you manage. The pipeline is the planning end of that journey, and the contract register is the published record at the other end.

Common problems

You can only see one view at a time: that is deliberate, so switch views with the control rather than looking for them side by side. The contract register is not one of the views: it is on the Contracts screen. A pipeline row opens somewhere unexpected: a quick request for quotes opens on its own Quick RFQ screen, which is intended, because it is a lighter process than a full requirement.