Open Tender and Contract Release Tags
1 minute
Open Tender and contract release tags indicate the stage a tender or contract process is at. This process allows for changes in the content this may result in a number of releases of information over time so several stages are available to the buyer. These are tagged within the Contract dataset in the ‘Tag’ column to indicate the stage of the tender or contract.
The tags are defined as part of the Open Contracts standards
| Title | Description |
|---|---|
| Planning | A contracting process is proposed or planned. Information in the tender section describes the proposed process. The tender.status field should be used to identify whether the planning is at an early pipeline stage, or whether there are detailed plans for a tender developed. |
| Planning Update | Details of a proposed or planned contracting process are being updated. This may include addition of information and documents from consultation engagement activities, revised details or timelines for a proposed contracting process, or a tender.status update to indicate that a pipeline proposal has been withdrawn. |
| Tender | Providing information about a new tender (call for proposals) process. Tender release should contain details of the goods or services being sought. |
| Tender Amendment | An amendment to an existing tender release. There should be at least one tender release with the same ocid, but an earlier releaseDate, before a tenderAmendment is published. The term amendment has legal meaning in many jurisdictions. |
| Tender Update | An update to an existing tender release. There should be at least one tender release with the same ocid, but an earlier releaseDate, before a tenderUpdate is published. An update may add new information or make corrections to prior published information. It should not be used for formal legal amendments to a tender, for which the tenderAmendment tag should be used. |
| Tender Cancellation | The cancellation of an existing tender. There should be at least one release with the same ocid, but an earlier releaseDate, which provides details of the tender being cancelled. |
| Award | Providing information about the award of a contract. The tender section may be populated with details of the process leading up to the award, and one or more award sections will be present. |
| Award Update | An update to an existing award release. There should be at least one award release with the same ocid, but an earlier releaseDate before an awardUpdate is published. An update may add new information or make corrections. |
| Award Cancellation | Providing information about the cancellation of an award. |
| Contract | Providing information about the details of a contract that has been, or will be, entered into. The tender section may be populated with details of the process leading up to the contract, and the award section may contain details of the award on the basis of which this contract will be signed. |
| Contract Update | Providing information about updates to a contract. There should be at least one contract release with the same ocid, but an earlier releaseDate, before a contractUpdate is published. An update may add new information or make corrections to prior published information. It should not be used for formal legal amendments to a contract, for which the contractAmendment tag should be used. |
| Contract Amendment | An amendment to an existing contract release. There should be at least one contract release with the same ocid, but an earlier releaseDate, before a contractAmendment is published. The term amendment has legal meaning in many jurisdictions. |
| Implementation | Providing new information on the implementation of a contracting process. |
| Implementation Update | Updating existing information provided about the implementation of a contracting process. |
| Contract Termination | Providing information at the end of a contracting process. |
| Compiled record | This tag is used only in compiled records, which have merged together multiple releases to provide a snapshot view of the contract, and a version history. |
