diff --git a/docs/history/changelog.md b/docs/history/changelog.md
index fd669c495..b860ba6b5 100644
--- a/docs/history/changelog.md
+++ b/docs/history/changelog.md
@@ -52,6 +52,7 @@ Per the [normative and non-normative content and changes policy](https://docs.go
 * [#1209](https://github.com/open-contracting/standard/pull/1209) Replace "electronic goods" with "digital goods" in the description of 'goods' from the `procurementCategory` codelist, to align with the description in the World Trade Organization's Agreement on Government Procurement, and to avoid confusion between electronic goods like computers and digital goods like software.
 * [#1210](https://github.com/open-contracting/standard/pull/1210) Add the 'CELEX' and 'LEXML' codes from the legal basis extension to the `itemClassificationScheme` codelist.
 * [#1218](https://github.com/open-contracting/standard/pull/1218) Add the 'COFOG' code from the organization classifiation extension to the `itemClassificationScheme` codelist.
+* [#1238](https://github.com/open-contracting/standard/pull/1238) Open the `releaseTag` codelist.
 
 ### Schema
 
diff --git a/docs/schema/codelists.md b/docs/schema/codelists.md
index b34eb9e51..6322939f9 100644
--- a/docs/schema/codelists.md
+++ b/docs/schema/codelists.md
@@ -21,6 +21,16 @@ Codes are case-sensitive, and are generally provided as English language camelCa
 
 ## Open Codelists
 
+### Release Tag
+
+A contracting process can result in a number of releases of information over time. These must be tagged to indicate the stage of the contracting process they relate to.
+
+```eval_rst
+.. codelisttable::
+   :header-rows: 1
+   :file: ../../build/current_lang/codelists/releaseTag.csv
+```
+
 ### Party Role
 
 The organizations, economic operators or other participants in a contracting process are listed in the [parties section](../reference/#parties). A single party can have one or more roles in the contracting process.
@@ -159,16 +169,6 @@ The extended procurement category codelist is used to provide additional detail
 
 ## Closed Codelists 
 
-### Release Tag
-
-A contracting process can result in a number of releases of information over time. These must be tagged to indicate the stage of the contracting process they relate to. 
-
-```eval_rst
-.. codelisttable::
-   :header-rows: 1
-   :file: ../../build/current_lang/codelists/releaseTag.csv
-```
-
 ### Initiation Type
 
 Contracting processes can be formed under a number of different processes. Currently, only 'tender' is supported in this codelist. Future versions of the standard might support other initiation types. The initiation type is used to provide information to consuming applications on the different blocks of data and releases they can expect from a contracting process.
diff --git a/schema/dereferenced-release-schema.json b/schema/dereferenced-release-schema.json
index 8f057dcd6..346144ba1 100644
--- a/schema/dereferenced-release-schema.json
+++ b/schema/dereferenced-release-schema.json
@@ -27,31 +27,13 @@
     },
     "tag": {
       "title": "Release Tag",
-      "description": "One or more values from the closed [releaseTag](https://standard.open-contracting.org/{{version}}/{{lang}}/schema/codelists/#release-tag) codelist. Tags can be used to filter releases and to understand the kind of information that releases might contain.",
+      "description": "One or more values from the open [releaseTag](https://standard.open-contracting.org/{{version}}/{{lang}}/schema/codelists/#release-tag) codelist. Tags can be used to filter releases and to understand the kind of information that releases might contain.",
       "type": "array",
       "items": {
-        "type": "string",
-        "enum": [
-          "planning",
-          "planningUpdate",
-          "tender",
-          "tenderAmendment",
-          "tenderUpdate",
-          "tenderCancellation",
-          "award",
-          "awardUpdate",
-          "awardCancellation",
-          "contract",
-          "contractUpdate",
-          "contractAmendment",
-          "implementation",
-          "implementationUpdate",
-          "contractTermination",
-          "compiled"
-        ]
+        "type": "string"
       },
       "codelist": "releaseTag.csv",
-      "openCodelist": false,
+      "openCodelist": true,
       "minItems": 1,
       "omitWhenMerged": true
     },
diff --git a/schema/release-schema.json b/schema/release-schema.json
index 3089002de..cb38167ef 100644
--- a/schema/release-schema.json
+++ b/schema/release-schema.json
@@ -27,31 +27,13 @@
     },
     "tag": {
       "title": "Release Tag",
-      "description": "One or more values from the closed [releaseTag](https://standard.open-contracting.org/{{version}}/{{lang}}/schema/codelists/#release-tag) codelist. Tags can be used to filter releases and to understand the kind of information that releases might contain.",
+      "description": "One or more values from the open [releaseTag](https://standard.open-contracting.org/{{version}}/{{lang}}/schema/codelists/#release-tag) codelist. Tags can be used to filter releases and to understand the kind of information that releases might contain.",
       "type": "array",
       "items": {
-        "type": "string",
-        "enum": [
-          "planning",
-          "planningUpdate",
-          "tender",
-          "tenderAmendment",
-          "tenderUpdate",
-          "tenderCancellation",
-          "award",
-          "awardUpdate",
-          "awardCancellation",
-          "contract",
-          "contractUpdate",
-          "contractAmendment",
-          "implementation",
-          "implementationUpdate",
-          "contractTermination",
-          "compiled"
-        ]
+        "type": "string"
       },
       "codelist": "releaseTag.csv",
-      "openCodelist": false,
+      "openCodelist": true,
       "minItems": 1,
       "omitWhenMerged": true
     },