Chapter 7 - Award of contracts and issuance of standing offers and supply arrangements

7.1 Overview of contract award and issuance of standing offers and supply arrangements

Effective date: 2023-03-30

1. This chapter describes the process of contract award to a successful bidder, as well as the issuing of the authorization to use a standing offer (SO) or a supply arrangement (SA) received from a successful offeror or supplier. It also provides general instructions for release of information to the public about the results of the bid solicitation.
2. Before award/issuance of the document, the contracting officer must ensure that the following elements have been appropriately addressed:
   1. industrial security requirements (see 3.55 Industrial security requirements (personnel or organization) and 5.15 Verifying compliance with security requirements);
   2. vendor performance corrective measures (see 8.180 Vendor Performance Policy);
   3. supplier financial capability or financial security (see 5.60 Financial capabilities of contractor);
   4. award/issuance is in accordance with the approval obtained and any exceptions to internal approval authorities (see article 1.1. of Annex 6.4.1: Approval authorities and additional signing authorities in support of clients' programs only - other than for Canadian Commercial Corporation);
   5. Integrity Provisions (see 5.16 Integrity compliance);
   6. Federal Contractors Program for Employment Equity (see Annex 5.1 Federal Contractors Program for employment equity).
3. Electronic Signatures: When awarding a contract or issuing a standing offer or supply arrangement, the contracting officer may choose to electronically sign the front page of the document using their MyKey (or a Public Key Infrastructure [PKI]) certificate) to self-authenticate. The contracting officer can then electronically sign the document using Adobe Acrobat or another PDF writer software after being prompted to self-authenticate using their MyKey (or a PKI certificate).

7.5 Contract award

Effective date: 2016-04-04

1. Contract award may take place at any time, after bid closing and completion of the evaluation, and before the bid validity expiry date. The contract document will depend on the type of bid solicitation.
2. A purchase order will be issued when quotations are received, either by way of a Request For Quotation (RFQ) or a telephone buy. If quotations were solicited by telephone, the supplier must confirm, in writing, the terms of the purchase order.
   Note: Prior to issuing a purchase order, contracting officers must follow the integrity verification process outlined in section 5.16 Integrity compliance.

3. A "Your Tender/Proposal is accepted" document will be issued when tenders/proposals are requested, and the bid is received in writing and accepted. This type of document is used when the contract reflects those conditions proposed, or agreed to in writing, by the successful bidder. The document should make reference to the bid and any amendments to it.
   Note: Construction contracts are awarded under a true bid and acceptance process. The bidder submits the completed bid and acceptance form, and Public Works and Government Services Canada (PWGSC) sends an acceptance document.

4. A "You are Requested" document is issued where the proposed contract may reflect a condition not agreed to in writing by the successful bidder. This constitutes a counter-offer by PWGSC and must be accepted by the successful bidder in writing to constitute a legally binding contract.
   Note: The "You are Requested" documents, and in some cases purchase orders, are not contracts but only offers by PWGSC to potential contractors. Although a legal contract does not exist, such offers usually reflect the contracting officer's understanding of the conditions, which are agreeable to the successful bidder. If the successful bidder does not accept the PWGSC offer, or proposes modifications to the contract, the matter should be referred to Legal Services.
5. Formal Agreements. Contracting officers must consult with Legal Services when considering this type of contract.

7.10 Issuance of supply arrangements and standing offers

Effective date: 2010-01-11

Following a Request for Standing Offers (RFSO) or a Request for Supply Arrangements (RFSA) process, an authorization document is issued, which gives contracting officers and client departments, when applicable, the authority to use the instrument. For more information on the use of these instruments, see 3.5 Existing procurement instruments, 3.15 Non-competitive contracting process, 4.10.20 Request for Standing Offers and 4.10.25 Request for Supply Arrangements.

7.10.1 Standing offers

Effective date: 2017-06-21

1. The authorization document for standing offers, entitled "Standing Offer and Call-Up Authority", may take one of the following forms:
   1. a "National Master Standing Offer (NMSO)", which is generally issued for the use of all departments. PWGSC contracting officers and client departments are both authorized to make call-ups;
   2. a "Departmental Individual Standing Offer (DISO)", which is generally issued for the use of a single client. Only PWGSC contracting officers are authorized to make call-ups. However, software DISOs, which are structured more like NMSOs, are an exception as they authorize the client to make call-ups;
   3. a "National Individual Standing Offer (NISO)", which is generally issued for the use of a single client. Both PWGSC contracting officers and client department are authorized to make call-ups;
   4. a "Regional Master Standing Offer (RMSO)", which is generally issued for the use of many clients within a specific geographic area; and
   5. a "Regional Individual Standing Offer (RISO)", which is generally issued for the use of a single client within a specific geographic area.
2. Call-ups must be made in accordance with the procedure set out in the SO and, in the case of multiple SOs, in accordance with the call-up methodology described in all of the SOs being referenced. Call-ups cannot exceed the contracting limit set out in the standing offer. For more information on allowable call-up limitations, see 4.10.20.1(a).
3. A call-up against a standing offer carried out by an identified user constitutes acceptance of the offer. The SO (offer) and call-up (acceptance) form a binding contract between Canada and the offeror. Several options can be used to issue a call-up under a SO:
   1. the Canada acquisition card (Visa or MasterCard) for low dollar value requirements
   2. PWGSC-TPSGC 942 Call-up Against a Standing Offer
   3. PWGSC-TPGSC 942-2 Call-up Against a Standing Offer - Multiple Delivery
   4. PWGSC-TPSGC 944 Call-up Against Multiple Standing Offers (English version)
   5. PWGSC-TPSGC 945 Commande subséquente à plusieurs offres à commandes (French version)

7.10.5 Supply arrangements

Effective date: 2010-01-11

1. The authorization to use a supply arrangement insert (SA) will take the form of a SA document that is generally issued for use by all client departments. Client departments may or may not be authorized to award contracts or issue bid solicitations. If authorized, they will award contracts under their own contracting authority within their own financial contracting authority. For contracts beyond client departments' contracting authority, PWGSC will be the contracting authority.
2. Resulting contracts must be awarded in accordance with the procedures, and within the contracting limits, described in the supply arrangement.

7.15 Legal entity

Effective date: 2010-01-11

1. Whatever the form of procurement document, the contracting officer must ensure that it is with a supplier that is a legal entity having the legal capacity to contract, and that the supplier's legal name is used.
2. Possession of a Procurement Business Number (PBN) is not equivalent to having the legal capacity to contract. The contracting officer must still verify that the supplier has the legal capacity to contract.
3. For example, a contract may not be awarded to a division of a corporation, as it is not a legal entity. Be aware that computerized source lists may include an abbreviated name for a supplier. In some cases, a legal entity (for example a numbered company) will use a business name to do business. In such cases, the legal name (the number of the company) must be used and it could be followed by "doing business as ______(insert the business name)".

7.20 Letter of Intent

Effective date: 2010-01-11

1. When the timely delivery of goods or services would be jeopardized by lengthy negotiations, a Letter of Intent authorizes commencement of the work before the contract is awarded. It is a binding commitment to place a contract with a designated supplier.
2. Letters of Intent can only be used in exceptional circumstances, and must not be issued without prior approval of the Deputy Minister (DM).
3. A Letter of Intent is issued subsequent to DM approval of the conditions already agreed to by the proposed contractor, but before obtaining contract approval of all the conditions of the proposed contract.
4. Letters of Intent are prepared by Legal Services with the cooperation of the contracting officer.
5. No contractual commitment may be made that would constitute the first step of a procurement that might require subsequent Treasury Board approval.
6. The Letter of Intent must accurately describe the work authorized, state the maximum liability of Canada, expressed as funds to be spent by the contractor, and specify how the payment will be made. The contract serial number that will be assigned to the subsequent contract must be indicated on the Letter of Intent.
7. After DM approval is received, the original Letter of Intent must be signed by the appropriate contract signing authority and distributed in the same manner as a contract.
8. On completion of negotiations of all the conditions of the proposed contract, the contract approval document will be submitted for review and approval at the appropriate level.
9. The contracting officer must clearly indicate in the contract that the work authorized under the Letter of Intent is not to be duplicated.

7.25 Go-ahead letters

Effective date: 2010-01-11

Go-ahead letters may be issued after obtaining final approval of the contract approval document, provided all appropriate conditions of the proposed contract are known and accepted by the proposed contractor. Go-ahead letters are subject to the appropriate signing authorities. After issuing the go-ahead letter, the contract must be sent to the contractor in a timely manner.

7.30 Procurement reporting and posting of award notices

Effective date: 2024-04-19

The following sections describe procedures that contracting officers must follow to meet departmental responsibilities for award notices and contract activity reporting. These requirements stem from legal requirements, corporate and government policies, parliamentary needs and departmental procedures. The following is a summary of reporting requirements:

1. Award Notices posted on the Government Electronic Tendering Service (GETS);
2. Purchasing Activity Reports (government-wide annual reporting);
3. Contract History database (published on Buyandsell.gc.ca);
4. Comprehensive Land Claim Agreement contract reporting;
5. Procurement Strategy for Indigenous Business reporting;
6. Trade agreements reporting requirements; and;
7. Specific procurement activities such as contracts with task authorizations, terminations and conditional amendments related to vendor performance.

Note: The above section is not written to address the complete reporting requirements of client departments or suppliers, but only of contracting officers in the Acquisitions Program of Public Works and Government Services Canada.

7.30.1 Award notices on the Government Electronic Tendering Service

Effective date: 2023-03-30

1. For procurements subject to the international trade agreements and the Canadian Free Trade Agreement (CFTA), an award notice must be posted on the Government Electronic Tendering Service (GETS) within 72 days of contract award.
2. For all contractual documents issued through the Electronic Procurement Solution (EPS), award notices are generated and posted on CanadaBuys.canada.ca, except when the "National Security" indicator is checked. See 7.30.30 Use of the National Security Indicator for more details.

7.30.5 Procurement activity reporting to Treasury Board Secretariat

Effective date: 2024-04-19

1. In 1996, Public Works and Government Services Canada (PWGSC) agreed with the Treasury Board Secretariat (TBS) that PWGSC would be responsible for collecting contract data from other government departments and agencies to generate the annual procurement activity reports. This annual activity entails the reporting of the following:
   1. federal contracting (on behalf of the Treasury Board Secretariat);
   2. federal contracting in respect of all Trade Agreements to which Canada is a signatory (on behalf of the Department of Foreign Affairs and International Trade);
   3. federal contracting in respect of the Canadian Free Trade Agreement and the Ownership of Intellectual Property (on behalf of the Department of Industry); and
   4. all procurements related to the Procurement Strategy for Indigenous Business (on behalf of Indigenous Services Canada).
2. PWGSC Contract: Contracts must be reported on an annual basis. The reports, summary or detail, should be submitted by the end of February. Such reports should include contract activity such as formal agreements, confirming orders, security sensitive contracts and any other contract or call-up not otherwise captured in automatic reporting.
3. Standing Offers and Supply Arrangements: In the past, departments and agencies have reported only the total contract activity under standing offer agreements instead of reporting details on individual call-ups as quite a number of departments did not have the capability to report against call-ups. Beginning in 2011, departments and agencies phased in the reporting of standing offer call-ups as part of the Purchasing Activity Reports. Effective January 2011:
   1. all call-ups issued by PWGSC contracting officers are captured in the Government Contract Activity Report;
   2. the value entered for the total estimated value, appearing on the front page of Standing Offers is no longer used as part of the contract activity report, regardless of the type of standing offer. Contracting officers within AB are not responsible for reporting client departments' contracts/call-ups which utilizes PWGSC SOs and SAs. This is reported to OSME-SE directly from the departments.

7.30.10 Contract history on Buyandsell.gc.ca

Effective date: 2023-03-30

The Contract History database for Public Works and Government Services Canada (PWGSC) common services procurement was originally launched to facilitate requests about contracts awarded by PWGSC, and is accessible to both suppliers and government buyers. Making this data readily available supports a reduction in access to information and privacy (ATIP) requests for information on contract awards. On March 8, 2013, this database was added to the Procurement Data section on BuyandSell.gc.ca, along with other data such as Standing Offers and Supply Arrangements (SOSA), and also Goods and Services Identification Number (GSIN) on June 1, 2013.

7.30.15 Comprehensive Land Claims Agreement reporting

Effective date: 2023-03-30

As detailed in Treasury Board Secretariat Contracting Policy Notice 2008-4, the government monitors and reports on procurements that are subject to Comprehensive Land Claims Agreements (CLCAs). Therefore, contracting officers must ensure that the procurements subject to CLCAs are identified accurately.

7.30.20 Procurement Strategy for Indigenous Business reporting

Effective date: 2024-04-19

1. The establishment of, and reporting on, annual objectives in support of the Procurement Strategy for Indigenous Business, includes value and numbers of contracts awarded to Indigenous businesses, supplier promotion activities, and increased representation of Indigenous businesses on department source lists.
2. Therefore, contracting officers must ensure that reporting on procurements subject to the Procurement Strategy for Indigenous Business (PSIB) is completed accurately. All procurements subject to PSIB must be identified as such.

7.30.25 Trade agreements reporting

Effective date: 2023-03-30

1. Some trade agreements, including the Canadian Free Trade Agreement (CFTA), Canada-European Union Comprehensive Economic and Trade Agreement (CETA), and the World Trade Organization Agreement on Government Procurement (WTO-AGP) require that parties report on covered procurement. In response to this obligation, Public Works and Government Services Canada provides statistics to the Treasury Board Secretariat who is responsible for the government-wide report.
2. Contracting officers are to ensure that when their procurement is covered by one or more of Canada’s trade agreements it is identified accurately to meet all trade agreements reporting obligations.
3. Contracts must be reported as per subsection d. of 7.30.5 Procurement activity reporting to Treasury Board Secretariat. Such reports must identify which trade agreements applied to the procurement.

7.30.30 Use of the National Security Indicator

Effective date: 2023-03-30

1. There may be circumstances other than National Security where posting an award notice could reasonably be expected to compromise government confidences, cause economic disruption, or similarly be contrary to the public interest. On the other hand, there are procurements for which a National Security Exception (NSE) was approved in accordance with paragraph 3.105 National Security Exceptions of the Supply Manual, but it is still appropriate to post an award notice.
2. A contracting officer may suppress the posting of an award notice.
3. Therefore, the following procedures apply with regard to the National Security Indicator:
   1. when an NSE is invoked for a procurement in accordance with paragraph 3.105 National Security Exceptions of the Supply Manual, and posting an award notice is contrary to the public interest, the contracting officer must suppress publishing for the original contractual document and for any subsequent amendments, thus no award notices will be posted for any documents.
   2. when an NSE is invoked in accordance with paragraph 3.105 National Security Exceptions of the Supply Manual, and posting an award notice is not contrary to public interest, both the original and subsequent amendment documents and the award notice will be posted.
   3. if an NSE does not apply, but the contracting officer’s management has advised that it is not in the public interest to post an award notice, the contracting officer must suppress the publishing for the original contractual document and for any subsequent amendment documents.

7.30.35 Reporting of contract with task authorizations

Effective date: 2013-06-27

After issuing a contract with task authorizations (TAs) or an amendment to this type of contract, contracting officers must report on the procurement. See section 7.70.35 Contracts with task authorizations - coding for instructions.

7.30.40 Reporting of emergency requirements

Effective date: 2022-05-12

Use of the emergency contracting authority is subject to the reporting requirement for such contracts as set out in the TB Directive on the Management of Procurement (see Appendix C, section C.5 Emergency Contracting for details).

7.35 Notification to unsuccessful bidders/offerors/suppliers

Effective date: 2010-01-11

Contracting officers should notify unsuccessful bidders/offerors/suppliers as soon as possible after contract award and issuance of a standing offer or supply arrangement. Samples of regret letters are provided in Annex 7.1: Samples of regret letters.

7.40 Debriefing and feedback session to bidders/offerors/suppliers

Effective date: 2022-07-21

1. Debriefing
   1. The purpose of a debriefing is to explain to unsuccessful bidders/offerors/suppliers why their bid/offer/arrangement was not accepted, allowing them to improve their future documents. A debriefing demonstrates the fairness, openness, and transparency of the federal government contracting process. Also, contracting officers can improve future solicitations by using the comments and suggestions provided by bidders/offerors/suppliers.
   2. Every solicitation must include a provision stating that bidders/offerors/suppliers may request a debriefing about the results of the solicitation. The departmental standard procurement templates include a provision to this effect.
   3. Following the award of a contract or issuance of a standing offer (SO)/supply arrangement (SA), a debriefing will be provided upon request. A written debriefing is usually done in the form of a regret letter that is sent out to each unsuccessful bidder/offeror/supplier. See samples of regret letters in Annex 7.1 Samples of regret letters.
   4. In the case of a complex procurement, when a solicitation is conducted in phases, the contracting officer will notify unsuccessful bidders/offerors/suppliers at the end of each phase and provide a debriefing upon request.
   5. Within the limits expressed at section 7.45 Disclosure of information, a debriefing will include the following, as applicable:
      1. the name(s) of the successful bidder(s)/offeror(s)/supplier(s);
      2. the total estimated cost of the contract(s);
      3. the total evaluated price of the successful bidder(s) and the total score, if applicable;
      4. very general information on the relative strengths of the successful bid(s)/offer(s)/arrangement(s), ensuring that confidential and commercial information is not divulged;
      5. an outline of the reasons the bid/offer/arrangement of the bidder/offeror/supplier being debriefed was not successful according to the evaluation criteria and selection methodology; and
      6. Scores achieved on all rated criteria of the bid/offer/arrangement, will be provided with sufficient detail for the bidder/offeror/supplier to understand why those scores were assigned.
2. Feedback Session
   1. A feedback session is a form of debriefing. A feedback session will be provided, upon request, when a solicitation is to be cancelled and reissued. The purpose of a feedback session is to provide the bidder/offeror/supplier with information specific to their bid/offer/arrangement. As an example, a feedback session will provide the bidder/offeror/supplier with information on which mandatory criteria they passed or failed or their overall technical score or their score for each technical criterion. This information will allow the bidder/offeror/supplier to understand why their bid/offer/arrangement failed to meet the requirements. No information regarding other bids/offers/arrangements or the solicitation to be reissued must be divulged.
   2. In order to ensure the fairness, openness, and transparency of the solicitation process, all bidders/offerors/suppliers must have access to the same information on the solicitation to be reissued. Therefore, all information provided in a feedback session must be documented by the Contracting Authority. The information communicated during the feedback session, where pertinent, will be provided in a generic form in the solicitation to be reissued to maintain fairness to all potential bidders/offerors/suppliers. One or both of the following measures will be taken to provide bidders/offerors/suppliers with this information:
      1. The particular area of concern will be highlighted more prominently with additional instructions to bidders/offerors/suppliers in the solicitation to be reissued (for example, by adding text to inform or focus attention).
      2. A bidders' conference will be held for the solicitation to be reissued. For further information on bidders' conferences, see section 4.30.45.15 Bidders' conferences and site visits.
   3. In determining which of these two measures, b. ii. A. and/or B., to use, contracting officers should consider the following factors:
      1. the complexity of the procurement or solicitation documents;
      2. the likelihood of an unsuccessful reissued solicitation, e.g. if no responsive bids/offers/arrangements had been received;
      3. the nature of the issues that created a need to cancel and reissue the solicitation;
      4. the sensitivity of the procurement; and
      5. the estimated dollar value of the procurement.
   4. Both measures listed in, b. ii. A. and B. above, must be undertaken when Treasury Board (TB) contract approval is required.
   5. In accordance with subsection f. of section 4.100 Cancelling and reissuing a solicitation, all solicitations to be reissued must include Standard Acquisition Clauses and Conditions (SACC) clause A9043T Reissue of Bid Solicitation, informing bidders/offerors/suppliers that the reissued solicitation cancels and supersedes the previous solicitation and that a debriefing or feedback session will be provided, upon request, to bidders/offerors/suppliers who bid on the previous solicitation.
3. Cancelled Solicitations
   1. When a solicitation is cancelled prior to the bid solicitation closing date, the Contracting Authority must adhere to the procedures addressed in section 4.100 Cancelling and reissuing a solicitation.
   2. When a solicitation is cancelled after the bid closing date but prior to completing the evaluation of mandatory or rated criteria, the Contracting Authority will inform bidders/offerors/suppliers of the cancellation and that the evaluation of the bids/offers/arrangements was not completed.
   3. When a solicitation is cancelled after the bid closing date, following the evaluation of mandatory or rated criteria, and a new solicitation is not planned or will not be issued, a debriefing will be provided upon request in accordance with section 7.40 Debriefing and feedback session to unsuccessful bidders/offerors/suppliers.
   4. When a solicitation is cancelled following the evaluation of mandatory or rated criteria and will be reissued, then a feedback session will be provided upon request.
      1. If the solicitation is cancelled because all bids/offers/arrangements are non-responsive or do not represent fair value and the Statement of Requirements of the solicitation to be reissued is significantly modified, bidders/offerors/suppliers will only be informed of which mandatory criteria(s) or rated criteria(s) requiring a minimum score were failed but no detail is to be provided as to why the bidders/offerors/suppliers failed each criteria. No information on other rated criteria(s) is to be provided.
      2. If the solicitation is cancelled because all bids/offers/arrangements are non-responsive or do not represent fair value and the Statement of Requirements of the solicitation to be reissued is not significantly modified, bidders/offerors/suppliers will be informed of which mandatory criteria(s) or rated criteria(s) requiring a minimum score were failed with sufficient detail for bidders/offerors/suppliers to understand why they failed each criteria. No information on other rated criteria(s) is to be provided.
      3. If the solicitation is cancelled for reasons other than those mentioned above, bidders/offerors/suppliers will only be informed of which mandatory criteria(s) or rated criteria(s) requiring a minimum score were failed but no detail is to be provided as to why the bidders/offerors/suppliers failed each criteria. No information on other rated criteria(s) is to be provided.

   Bidders/offerors/suppliers will be advised not to make any assumptions from the information received regarding the cancelled solicitation when bidding on the solicitation to be reissued as evaluation criteria(s) may change.

4. Bidders/offerors/suppliers should request a debriefing or feedback session within fifteen (15) working days of receipt of the results of the solicitation process or cancellation of the solicitation process.
5. A debriefing or a feedback session should be provided within ten (10) working days from the date a request was received.
6. A debriefing or feedback session can be provided in writing, by telephone or in person. Contracting officers are to determine which method will be most effective in the context of a particular procurement. To the extent possible, any request for an in-person debriefing or feedback session, or for the information to be provided in a particular way, should be accommodated.
7. Contracting officers should consult with management and, if required, legal services prior to providing a debriefing or feedback session for a requirement that is sensitive or high risk.
8. If a fairness monitor was present during the evaluation process, then the contracting officer will advise the fairness monitor of the date and time of any telephone/in-person debriefing or feedback session or bidders' conference.
9. If legal counsel is to accompany the bidder/offeror/supplier to any in-person debriefing or feedback session, or participate in any telephone debriefing or feedback session, the contracting officer will inform Legal Services and discuss their participation.
10. Contracting officers must keep a record of the debriefing or feedback session information provided including, but not limited to, minutes or a record of any meeting and comments and suggestions from the bidders/offerors/suppliers.

11. Upon request, contracting officers should provide to bidders/offerors/suppliers the following general information about the judicial and quasi-judicial bodies to which bid protests can be made. For any given procurement, one or more of the following avenues may be available to a bidder/offeror/supplier that wishes to make a claim regarding the conduct of the procurement:

    1. Canadian International Trade Tribunal (CITT): Whether or not the CITT has jurisdiction to conduct an inquiry regarding any particular procurement will depend on factors such as the government institution conducting the procurement, the estimated value of the procurement, and the nature of the goods, services, or construction services being procured. More information can be obtained by visiting the How to File a Complaint section on the CITT Web site.
    2. Office of the Procurement Ombudsman (OPO): If the value of the procurement is below the monetary thresholds established under the Canadian Free Trade Agreement, the OPO may have jurisdiction to conduct a review. More information can be obtained by visiting the Make a Complaint section on the OPO Web site.
    3. An action in a Provincial/Territorial Superior Court or in Federal Court.

    Note: There are strict deadlines for bringing bid protests, and the time periods vary depending on where the bid protest is brought. Suppliers may wish to consult their own lawyers on the appropriate forum for bringing a bid protest.

7.45 Disclosure of information

Effective date: 2022-07-21

1. Formal requests through the Access to Information Act will be addressed by the Access to Information and Privacy Office.
2. The following information can be released by contracting officers on a routine basis, after award of a contract or after the issuance of a standing offer (SO) or supply arrangement (SA):
   1. for all solicitations for goods and services, the name of the successful and unsuccessful bidders/offerors/suppliers and whether the bid/offer was responsive or non-responsive. Since information on bidders/offerors/suppliers who are individuals may qualify for exemption under the Privacy Act, such situations should be directed to the Access to Information and Privacy Office as indicated in 7.45.c.; and
   2. for all goods and services requirements subject to public opening, information which was released at the public opening of bids; for example, name of each bidder and the total amount of each bid.
3. While informal requests on elements identified in 7.45.b. may alternatively be referred to the Access to Information and Privacy Office, the following types of informal requests for bid, contract or standing offer and supply arrangement information should be referred to the Access to Information and Privacy Office:
   1. information pertaining to classified requirements;
   2. names of bidders/offerors who are individuals and the content of their bids/offers, including prices, since such information may be subject to an exemption under the Privacy Act;
   3. copies of bids/offers, including any accompanying supplier catalogues, handbooks or pricing guides;
   4. copies of contracts, purchase orders or standing offer documents, including any accompanying supplier catalogues, handbooks, pricing guides and PWGSC-produced catalogues, handbooks, or acquisition guides;
   5. information contained in bids/offers/arrangements that have been cancelled or superseded by later bids/offers;
   6. individual unit pricing and labour rates whether contained in bids/offers, contracts, standing offers (SOs), supply arrangements (SAs) or purchase orders (disclosure will be assessed in accordance with the specific terms of each legal document concerned and discretion will be applied); and
   7. any other information not covered in b. above.

7.50 Bid and contract security

Effective date: 2010-01-11

1. Surety bonds lapse automatically on expiration of the purpose or period for which they were required. Security deposits (government guaranteed bonds, bills of exchange, irrevocable standby letters of credit) must be returned to bidders. The bidder must return the letters of credit to the issuer to complete the discharge.
2. Lapsing of surety bonds or return of security deposits (government guaranteed bonds, bills of exchange, irrevocable standby letters of credit) must occur in the following way for all requirements except construction:
   1. for all bidders, at the expiration of the bid validity period, either as originally set or as extended;
   2. for unsuccessful bidders, prompt notification or return of a security deposit, immediately after a contract is awarded, is essential in such cases so as not to constrain the their ability to make new bids;
   3. for a successful bidder, if no contract security is required, immediately upon award of a contract or, if contract security is required, once the contract security is received; and
   4. if contract security is required, the contract must be awarded before bid security lapses, if applicable, but not before the contract security has been received.
3. Lapsing of surety bonds, or return of security deposits (government guaranteed bonds, bills of exchange, irrevocable standby letters of credit) for construction requirements must occur as soon as practical following:
   1. the bid solicitation closing date, for those bidders submitting non-compliant bids;
   2. the administrative bid review, for those bidders submitting compliant bids ranked fourth to last on the schedule of bids;
   3. the award of contract, for those bidders submitting the second and third ranked bids; and
   4. the receipt of contract security from the successful bidder; or
   5. the cancellation of the bid solicitation, for all bidders.
   6. If one or more of the bids ranked third to first is withdrawn or rejected for whatever reason, then Canada should reserve the right to hold the bid security of the next highest ranked compliant bid in order to retain the bid security of at least three valid and compliant bids.
4. For construction services requirements, if contract security is required, the security must be received within 14 days after contract award and before bid security lapses.

7.55 Contract security requirements

Effective date: 2022-05-02

1. For every proposed procurement, the client departments must identify the security requirements by completing a Security Requirement Check List (SRCL) or else certify in writing that there are no security requirements (date of no security requirement must be included).
2. The contracting officer must verify with the Contract Security Program (CSP), and not by using the security indicator from the Vendor Information Management (VIM) system, that the proposed contractor meets the security requirements before contract award. For more information, see 5.15 Verifying compliance with security requirements.
3. Contracting officers must include a comment on the front page of the contract, standing offer, or supply arrangement, as follows:
   "THIS DOCUMENT CONTAINS A SECURITY REQUIREMENT (specify date of statement)"
   OR
   "THIS DOCUMENT CONTAINS NO SECURITY REQUIREMENT (specify date of statement)"
4. If applicable, the document index shall contain the block entitled:
   "Security Requirement(s)"
   AND, if applicable
   "Location(s) of Work Performance"
5. If the contract, standing offer or supply arrangement contains security requirements, the contracting officer must forward a copy of the contract, standing offer or supply arrangement, and any amendments, or revisions, to the CSP within two working days of the document being issued. Contracting officers may send a PDF version of the document by e-mail to tpsgc.ssicontrats-isscontracts.pwgsc@tpsgc-pwgsc.gc.ca.
6. When contracting for destruction of protected and classified government materials, contracting officers must be aware of the additional measures required and manage the risks associated with the destruction of protected and classified government materials. The Corporate Security Technical Standard defines PWGSC corporate policy and procedures relating to classified waste destruction, and should follow the interim standard, regarding classification levels of shredders, and complete the appropriate form ARC 0203, Request for Non-Accessioned Disposal, for the destruction of sensitive documents.
   PWGSC threshold may be exceeded when administering destruction contracts on behalf of other client departments, based on the client's threat risk assessment. If such is the case, the client may develop a security guide as amplifying instructions, which is to be attached to the Security Requirements Check List (SRCL) and the Statement of Work.
7. Important: For foreign classified information, consult with the CSP’s International Industrial Security Directorate (IISD) before undertaking destruction.

7.60 Environmental considerations

Effective date: 2021-12-02

This section has been removed as it is no longer relevant.

For reference purposes, section 7.60 is available in the Supply Manual Archive (accessible only on the Government of Canada network), Version 2021-1.

7.65 Proactive disclosure

Effective date: 2020-05-04

1. Client departments are required to report on a quarterly basis on contracts awarded with a value over $10,000, an amendment with a value over $10,000, and an amendment when it modifies the initial value of a contract to an amended contract value that is over $10,000. Departments are required to include information on contracts and contract amendments regardless of dollar value, excluding those entered into via acquisition card at $10,000 or less awarded to a former public servant in receipt of a Public Service Superannuation Act (PSSA) pension on the Proactive Disclosure website.
2. Contracting officers for common services should be providing the required information to client departments in a timely manner to facilitate their reporting process. For further information, consult the Guidelines on the Proactive Disclosure of Contracts on the Treasury Board of Canada Secretariat website.

7.70 Coding procedures

Effective date: 2013-06-27

Statistical information pertaining to PWGSC contracting activities is required to meet corporate and parliamentary needs. Contracting officers are responsible for ensuring the complete and accurate recording of all contracts.

7.70.5 Public Works and Government Services Canada reporting (common services)

Effective date: 2023-03-30

1. The Acquisition Information System (AIS) database contains over 16 full years of historical contracting data beginning with calendar year 1993. AIS is a relational database. It is a collection of information organized in related tables. A table is a collection of information about a certain topic. It contains data about contracts, requisitions, solicitations, notices, organizations, vendors and customers. AIS feeds data to the Contract History application on Buyandsell.gc.ca.
2. Contracting officers must follow the coding procedures in the Contract Coding Reference Guide (accessible only on the Government of Canada network).
3. The Contract Coding Reference Guide contains a list of elements and definitions found in the Procurement Summary Release Document. The Procurement Summary Release Document is completed by the contracting officer and the information it contains is then released to AIS.

7.70.10 Coding of Advance Contract Award Notice results

Effective date: 2023-03-30

This section has been removed in support of procurement modernization and the ongoing transition to CanadaBuys.

For references purposes only, section 7.70.10 is available in the Supply Manual archive (accessible only on the Government of Canada network), Version 2022-3.

7.70.15 Coding of region of delivery

Effective date: 2023-03-30

When entering the delivery points information for a standing offer or supply arrangement, contracting officers must identify those provinces or territories where potential deliveries may occur.

7.70.20 Coding of call-ups

Effective date: 2014-03-01

Call-ups are coded as competitive or non-competitive depending on the procurement strategy used on the underlying Standing Offer.

1. If a Standing Offer is issued competitively, with a clear ranking methodology for issuing call-ups in accordance with section 4.10.20.5 Ranking and methodology for Standing Offers, then the resulting call-ups are considered competitive and must be coded accordingly.
2. A Standing Offer that uses the Advance Contract Approval Notice is considered competitive for approval purposes only; call-ups resulting from a Standing Offer subject to an Advance Contract Award Notice (ACAN) posting must be coded as non-competitive.
3. If a Standing Offer is issued using a non-competitive (sole-source) procurement strategy, or does not have a clear ranking methodology (e.g. the client can choose which firms to issue call-ups), then the resulting call-ups are considered non-competitive and must be coded accordingly.

7.70.25 Coding of terminations and conditional amendments

Effective date: 2023-03-30

This section has been removed in support of procurement modernization and the ongoing transition to CanadaBuys.

For references purposes only, section 7.70.25 is available in the Supply Manual archive (accessible only on the Government of Canada network), Version 2022-3.

7.70.30 Comprehensive Land Claims Agreement coding

Effective date: 2023-03-30

This section has been removed in support of procurement modernization and the ongoing transition to CanadaBuys.

For references purposes only, section 7.70.30 is available in the Supply Manual archive (accessible only on the Government of Canada network), Version 2022-3.

7.70.35 Contracts with task authorizations - coding

Effective date: 2023-03-30

Contracting officers must code contracts with Task Authorizations (TAs).

Automated Data Capture (ADC) users must include the following statement when submitting the ADC procurement report: "Program ID: Contract that allows Task Authorizations".

Annexes

Consult the list below of annexes related to Chapter 7 - Award of contracts and issuance of standing offers and supply arrangements. 

• 7.1 - Annex: Samples of regret letters

  • 7.1.1 - Appendix A: Regret letter to unsuccessful bidders/offerors/suppliers - responsive bid/offer/arrangement

  • 7.1.2 - Appendix B: Regret letter to unsuccessful bidders/offerors/suppliers - non-responsive bid/offer/arrangement