Archived [2012-10-31] - Guidelines on the Proactive Disclosure of Contracts

1.1 To provide guidance to managers and functional specialists on the identification, collection and publication of contract information that is to be proactively disclosed.

2.1 The government proactively discloses information on contracts over $10,000, founded wrongdoing, grants and contributions over $25,000, position reclassification and travel and hospitality expenses. The proactive disclosure of contracts reflects broader government commitments to transparency and strengthened accountability within the public sector originally announced in Budget 2004.

2.2 These guidelines support the Treasury Board Contracting Policy. Section 5.1.4 of the Treasury Board Contracting Policy states that "Deputy heads are required to publicly disclose quarterly, within one month after the close of each quarter, contracts entered into or amendments valued at over $10,000."

3.1 Identification of contracts to be proactively disclosed

3.1.1 In the interests of transparency, it is recommended that departments publish information about their approach and practices related to the proactive disclosure of contracts, options, other amendments, standing offers, supply arrangements, task authorizations, disclosure exceptions and data elements on their departmental proactive disclosure websites.

3.1.2 Treasury Board Contracting Policy requires disclosure of the following:

• A contract when its value is over $10,000;
• An amendment when its value is 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.

3.1.3 When a series of amendments to a contract clearly exceeds $10,000, the series of amendments may be disclosed as one amendment. When a series of amendments occurs over more than one reporting period when the threshold of $10,000 is clearly exceeded only during the last reporting period, the series of amendments may be disclosed as one amendment in one reporting period. Alternatively, an amendment may be reported separately if this is the standard practice in the department.

3.1.4 Non-financial and negative amendments do not need to be disclosed, except when it is in the public interest to do so (for example, the cancellation of a large military procurement).

3.1.5 When a contract is awarded and subsequently terminated, the original contract information reported should not be modified.

3.1.6 A contract option, when exercised, may be disclosed as an amendment. Alternatively, the full value of a contract, including options, may be disclosed at the time of contract award.

3.1.7 A call-up against a standing offer or supply arrangement should be disclosed as a contract.

3.1.8 A standing offer agreement and a supply arrangement agreement are not procurement contracts but are to be disclosed for the purpose of transparency. When a department publicly discloses information about a standing offer agreement or a supply arrangement agreement on a website, the department may omit this agreement from its proactive disclosure report.

3.1.9 For contracts with task authorizations, ^[1] the full potential value of the contract may be disclosed upon contract award unless the full value is not expected to be used. In the latter situation, each task authorization may be disclosed individually. When a contract includes a fixed deliverable and another deliverable that requires a task authorization, the department may disclose the contract and task authorizations in any manner that is transparent.

3.1.10 The government commitment is to disclose contracts or amendments valued at over $10,000 with only very limited exceptions, such as national security. A department may withhold information regarding the following:

1. Memoranda of understanding with other levels of government and foreign governments;
2. Service level agreements between federal departments or with Crown corporations; and
3. Information about contracts whose proactive disclosure would compromise criminal investigations, national security or public safety. ^[2]

3.1.11 When a department determines that information about a contract is exempt from proactive disclosure under Section 3.1.10(c) of these guidelines, the department is encouraged to disclose information that is unclassified. If all of the information about a contract is exempted but can be disclosed at a later date, the department may include the contract in the next report.

3.2 Collection of contracting data elements

3.2.1 The following data elements were developed to provide consistency to the public. Specific information regarding each of the data elements is provided in the following subsections with a summary table provided in Appendix A. As a best practice, departments are encouraged to follow the recommended approach for each data element if possible. If use of the recommended approach is not possible, a department may use a standard practice in the department for disclosure. To provide consistency to the public, it is recommended that departments move away from departmental standards and move towards the recommended reporting standard over time.

1. Vendor name
   1. It is recommended that the vendor name be the legal name of the company, as indicated on the contract. Alternatively, the vendor name may be the name in the financial system if this is the standard practice in the department.
2. Reference number
   1. It is recommended that the reference number be the contract number. Alternatively, the reference number may be the commitment number or requisition number if this is the standard practice in the department.
3. Contract date
   1. It is recommended that the contract date be the date the contract is awarded by the government. Alternatively, the contract date may be the hard commitment date (the date that the financial commitment is recorded in the departmental financial system) if this is the standard practice in the department.
   2. It is recommended that the contract date for a contract with task authorizations be the date that the contract is awarded (or the hard commitment date) for the contract. When the full value of the contract with task authorizations is likely not to be used, the contract date for each task authorization may be the date that each task authorization is issued (or the hard commitment date).
   3. It is recommended that the contract date for an amended contract or the exercising of an option be the date that the contract is awarded (or the hard commitment date).
   4. It is recommended that the contract date for a confirming order be the date of the verbal contract for goods, services or an amendment. If the date of the verbal contract cannot be determined, the contract date may be the date that the confirming order is issued.
   5. Dates are to be expressed in numeric terms, using the following standard convention:
       
      
      2008-05-10
      (Year-Month-Day)
4. Description of work
   1. The description of work is recommended to be the economic object code and its description. A list of economic object codes and their descriptions can be found on the Department of Public Works and Government Services (PWGSC) Government-wide Chart of Accounts website. Alternatively, the description of work may be the Goods and Services Identification Number (GSIN) if this is the standard practice in the department. A list of the GSINs and their descriptions can be found on the Business Access Canada website.
   2. When a contract involves more than one economic object, it is recommended that the economic object associated with the largest dollar value be used. A department may use a different approach if this is the standard practice in the department.
   3. A department may provide additional text to supplement the economic object information.
5. Contract period or delivery date
   1. For a goods contract, it is recommended that the delivery date be the date that the goods are to be delivered. The department may use the last delivery date if the contract involves multiple items on multiple dates.
   2. For a services contract, it is recommended that the contract period be the period of time over which the services are provided. For example, from April 1 to August 31, 2008. For a standing offer or supply arrangement, it is recommended that the contract period be the period of time over which a call-up may be entered into.
   3. For a contract with task authorizations, it is recommended that the contract period or delivery date be the period of time over the entire contract for goods or services contracts. For a contract with task authorizations where the full value of a contract with task authorizations is likely not to be used, it is recommended that the contract period or delivery date be specified for each task authorization.
6. Contract value
   1. It is recommended that the contract value be the amount of the hard commitment recorded in the departmental financial system at the time of contract award. It is recommended that the contract value be shown in Canadian currency and include all applicable taxes.For a multi-year contract it may be the total amount of the contract for all years.
   2. For an amendment, it is recommended that the contract value be the amended contract value. It is also recommended that the original contract be included in the comments data element, with a remark that the contract has been amended.
   3. Departments may add additional data elements or subdivide this data element for the reporting of the original value and the value of the amendment.
   4. For a contract with task authorizations, it is recommended that the contract value be for the full amount of the contract rather than the amount specified within the minimum work guarantee clause. For a contract with task authorizations when the full value of the contract is likely not to be used, the contract value may be the value of each task authorization.
   5. The contract value for the proactive disclosure of a standing offer agreement or supply arrangement agreement is $0.
7. Comments
   1. Standardized comments are recommended to be used (refer to Appendix B). Avoid the use of acronyms within the comments data element.
   2. Departments are encouraged to provide a brief description of each contract so that the public may benefit from additional context. For example, for a management consulting contract the comments could state, "Feasibility study of a green building standard for departmental projects." As a minimum, departments may provide the title of the contract.

3.3 Publication of contracts on departmental websites

3.3.1 Departments may report their contracting data on their departmental websites. When PWGSC or another department or Crown corporation issues a contract on a department's behalf, the client department should report the contract.

3.3.2 When more than one department is funding the contract, the department signing the contract may report the contract. However, if PWGSC is signing the contract for more than one department, one client department may report the full value of the contract. For a standing offer agreement or supply arrangement agreement, it is recommended that the agreement be reported by the department that authorizes the agreement.

3.3.3 Reporting is to occur on a quarterly basis, corresponding to the government fiscal year quarters. Contract information is to be posted online within 30 days of the end of each reporting period.

3.3.4 When the above dates for posting fall on a weekend or statutory holiday, departments may post information by the last business day before the weekend or holiday in question.

3.3.5 A contract or amendment not reported in the reporting period in which it was awarded may be reported in the subsequent reporting period, or as soon as practicable.

3.3.6 Information posted in one reporting period can be modified in a subsequent reporting period only when a material error was made in the data originally reported. Any modified information is recommended to be clearly indicated as such within the previous report's comments data element and notice of the modification is to be provided within the comments data element of the current report (refer to Appendix B).

3.3.7 Contract information on departmental websites should be consistent with Treasury Board Common Look and Feel Standards for the Internet 2.0 (CLF 2.0). A Proactive Disclosure intranet site exists to facilitate navigation and ensure consistency.

3.4 Monitoring of proactive disclosure

3.4.1 In accordance with Section 4.1.8 of the Treasury Board Contracting Policy, departments are responsible for ensuring that the contracting authority (the minister) is acting and seen to be acting within the letter and the spirit of the Treasury Board Contracting Policy. The department runs the risk of non-compliance if it does not ensure that contract information is accurate, up to date and posted in accordance with these guidelines. It is recommended that the department's chief financial officer (CFO) or equivalent be responsible for ensuring that data reported is appropriately validated, complete and reported in a timely manner. It is a best practice for departments to clearly indicate any limitations associated with the data on the departmental website.

Relevant legislation:

• Access to Information Act
• Federal Accountability Act
• Financial Administration Act

Treasury Board policies:

• Contracting Policy
• Policy on Classification and Coding of Financial Transactions

Treasury Board standards:

• Common Look and Feel Standards for the Internet (CLF 2.0)

Other publications:

• Budget Speech 2004

Please direct enquiries about this guideline to your departmental headquarters. For interpretation of these guidelines, departmental headquarters may contact:

Please direct enquiries about the Government of Canada's Proactive Disclosure Initiatives to your departmental headquarters. For direct enquiries about the Government of Canada's Proactive Disclosure Initiatives, departmental headquarters may contact: