Match a specific procurement, contract-management or payment concern to PPRS or a wider compliance issue to PCS, using a clear evidence record.
A supplier concerned about a UK public procurement needs to identify the problem it wants reviewed before choosing the route. A disputed score, an overdue invoice, a barrier in a live competition and a pattern of poor practice across several procurements do not present the same question or call for the same evidence.
The Cabinet Office's current Procurement Compliance and Oversight page, updated in August 2026, separates the Public Procurement Review Service from the Procurement Compliance Service. PPRS addresses suppliers' concerns about particular procurements, contract management and late payment; PCS generally examines systemic or institutional compliance with the Procurement Act 2023. The distinction helps a business prepare a focused account of the issue before approaching either service.
Start with the notice or contract reference, contracting authority, applicable documents and the company's role. The service reviewing the concern needs to understand which process or contract is involved. A description such as our government customer does not identify the buyer or establish the relationship between the company and the procurement.
For a hypothetical specialist providing training services through a prime contractor, the concern may arise from the subcontract but relate to a public contract further up the chain. The supplier should identify that chain using the records it holds and distinguish its direct customer from the public authority. It can then explain which action or omission has caused the difficulty.
The PPRS scope and remit accepts relevant supplier or representative concerns about specific procurements, including supply-chain and valid, undisputed late-payment issues. It uses a two-year issue window and identifies authorities and circumstances outside its scope. Read those boundaries against the actual case rather than assume that every public-sector concern belongs with this service.
A useful account separates what happened from why the company believes it was wrong. For example, the factual record may show that a clarification was issued after the stated response deadline, that an invoice acknowledgement exists without a remittance, or that the published evaluation explanation does not address identified evidence.
The supplier can then connect the concern to the relevant document or practice. This avoids relying on a general allegation of unfairness while leaving the reviewer to discover the actual event. It also makes the company's own understanding easier to check: sometimes the notice, clarification and internal bid record refer to different document versions.
For the training supplier, a concise chronology might identify the completed service, invoice number, receipt acknowledgement, payment term and later correspondence. If the customer has disputed an item, include that fact and the stated reason. A collection problem described as undisputed becomes harder to assess if the supporting correspondence shows an unresolved disagreement over scope.
Begin with a short explanation of the issue and the documents that establish it. Name attachments by date and purpose and identify the relevant passage or event. The reviewer should be able to follow the concern without reading every email the company has exchanged during the contract.
Retain the full underlying record internally. A concise submission is easier to assess when it can be supported promptly if further information is requested. For a tender concern, the relevant materials may include the applicable invitation, clarification, submitted response and assessment explanation. For payment, they may include the contract terms, invoice, receipt evidence and the customer's replies.
The guide to UK assessment summaries helps distinguish a problem with the assessed offer from a question about the process or explanation. That preliminary reading can make a concern more precise. It also prevents the company from asking an oversight service to resolve a commercial disappointment that its own records do not establish as poor practice.
The PPRS remit describes investigations and non-binding recommendations; it does not act as the supplier's representative or have power to force a buyer to delay or suspend an award. For completed procurements, recommendations commonly concern improving future practice. The company's desired outcome should take account of that role.
A supplier seeking payment may want the relevant contract manager to address an overdue invoice. A supplier concerned about a process may want the authority to examine a documented issue or change its future practice. Those are concrete purposes. They are different from assuming that acceptance of a concern will produce a contract award or a particular financial remedy.
The company should also decide how it will manage the commercial relationship while the concern is considered. Continue to distinguish agreed delivery obligations from the matter being reviewed. An internal owner can coordinate communications so that the service team, finance and senior management provide a consistent factual account instead of sending conflicting explanations through several channels.
The PPRS remit says involvement is suspended during mandatory standstill and where relevant legal proceedings are underway, including after a pre-action letter. It also identifies other formal proceedings and statutory investigations among situations it does not normally investigate. These limitations make it essential to read the service's current remit before relying on it for a time-sensitive case.
The practical point is about coordination. If the company is considering a formal challenge, the person responsible for that decision needs the procurement dates and the status of any other approach. A review-service submission should not be treated as changing a separate legal deadline or as providing a substitute for advice on the available remedy.
Preserve the relevant dates independently. The award-notice and contract-details guide explains why publication of an award intention and entry into the contract are different events. A company deciding how to respond needs the actual event sequence, not a general impression that the award process is nearly finished.
PCS can receive concerns from anyone about Procurement Act compliance and generally focuses on institutional or systemic issues. The official page says it does not investigate specific decisions in an individual procurement in the way a supplier with a vested interest might seek. It also explains that not every referral leads to investigation.
For a business that has observed several similar problems, organise the evidence by procurement rather than claim a pattern from one ambiguous incident. Identify what recurs, what differs and which records support each example. A repeated inconvenience is not automatically the same thing as repeated non-compliance; the account should explain the specific practice being questioned.
Where the evidence relates to one supplier's contract-management or payment issue, the individual route may be the clearer starting point. The PCO page describes the services' ability to connect cases and patterns, so a supplier does not need to manufacture a systemic argument simply to make its concern sound more significant.
Before proceeding, assign one owner to the proposed submission and have another person check the chronology against the documents. State what the company wants reviewed, which route appears relevant and what information remains uncertain. If an invoice has since been paid or a buyer has issued a correction, update the account before it is sent.
That preparation has value even where the company resolves the issue directly. It gives management a clear view of the event, the evidence and the realistic next step. A well-supported concern is easier for a buyer or review service to address because it identifies a specific procurement problem and an intelligible request, with the commercial and procedural context preserved.
August 2026 PCO service page and current PPRS remit read on 6 September 2026. Specific-case, standstill and proceedings limitations are distinguished; no referral or external communication has been made.
Suggest a correction