In order for main suppliers to share their code to provide Supplier Information, Contracting Authorities will need to retrieve their Buyer API Token/Key from CDP and submit this on Panacea. This is required for Panacea, an e-Sender, to pull the information for the Supplier on your behalf.
Information on the PSQ (Procurement Specific Questionnaire)
The information below is taken from official guidance found here. This has the most up-to-date guidance and documentation for the PSQ, as published by the government.
- The Procurement Specific Questionnaire (PSQ) has been designed by the Government to support CA (Contracting Authorities) to comply with & operate effectively under the new regime. The PSQ fulfils a similar role to the Standard Selection Questionnaire (SQ) used under the Public Contracts Regulations 2015 (PCR). The PSQ complements existing guidance for the Procurement Act 2023 and also central government policies and best practice, including Cabinet Office Procurement Policy Notes and Playbooks.
- The Procurement Regulations 2024 change the way suppliers share certain information: This includes the requirements on CA's to obtain confirmation from suppliers that they have registered, submitted & shared up-to-date core Supplier Information via the central digital platform (CDP).
- The PSQ is relevant for above-threshold procurements under the Act, which commenced from 24th February 2025.
- It does not apply to procurements commenced (or contracts awarded) before 24/02/2025 .
- It does not apply to contracts awarded via frameworks, dynamic purchasing systems (DPS) or qualification systems under the previous regime.
PA23 - PSQ Template & Supplier Share Code Question
We have added Tender Templates on all relevant sites for the PA23 PSQ (Procurement Specific Questionnaire) so that our subscribers can start updating/building their new Tender Templates in accordance with the legislation.
Supplier "Share Code" Question
To support the legislation, we have created a Question type in Tender Questionnaires called Share Code. This will ask the suppliers to provide their Supplier Share Code from CDP (there will also be a link to CDP so that the supplier can easily navigate to CDP to obtain the code/update their details).
N.B. This Question Type will always be mandatory when asked.
Through the API, the software will gather the Supplier Information that has been provided by the Supplier. It will then present this information in a pop-out snapshot to the Supplier to check the information when filling out their response. It will also present as a pop-out snapshot to the Contracting Authority/evaluators when evaluating the response.
Within the "Part 1 - Confirmation of Supplier Information" section, we have designed the template so that the main supplier can choose to either provide their Share Code through the API, OR if they are unable to do this, to provide an upload of their information from the CDP.
For the details of associated persons (including sub-contractors), these suppliers do not have to provide all of the Supplier information from CDP like the main Supplier does as this is not required under the legislation. As such, we strongly recommend asking the main supplier to provide zip files of the relevant files for their associated persons, rather than using the Share Code type. This is how we have designed the template.
Things to note:
- We have built the template in accordance with the latest version of the PSQ published by the Government in late December 2024. The Government are still making edits to the PSQ, so we advise all Contracting Authorities to monitor this link.
- Reminder: For the Share Code question to work, you must ensure that you have submitted your Buyer API Token/Key onto Panacea. CDP requires e-Senders to use the Buyers API Token/Key in order to retrieve the Supplier Information. e-Senders are not authorised to do this without this.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article