Four state names are enough to stop most arguments, if the project uses them consistently. Suitability and revision sit beside the state. They are not the same thing. The states belong to the project’s CDE workflow; if you are unsure whether a shared drive counts, read what a CDE is first. This page is about the states themselves and the gates between them.
The states at a glance
| State | Who can see it | Can others rely on it? | Typical next step |
|---|---|---|---|
| Work in progress | The producing task team | No | Check, review and approve within the task team, then share |
| Shared | The wider delivery team, and the appointing party where agreed | For coordination and comment only | Revise in WIP, or put forward for authorisation |
| Published | Those who need it for the stated purpose | Yes, for that purpose | Replaced by a later accepted revision |
| Archive | Read-only record | Only as evidence of what was issued | None; it stays as the record |
The gates between states
Most problems happen at the transitions, not inside a state. ISO 19650 describes three gates, and each has a different owner:
- WIP to Shared: check, review and approve. The task team checks its own container against the project’s standards and methods before anyone else sees it. Naming, metadata and the suitability code are part of that check.
- Shared to Published, first half: review and authorise. The lead appointed party reviews the delivery team’s shared information against the requirements and the plan, and authorises it to go forward, or sends it back.
- Shared to Published, second half: review and accept. The appointing party reviews it against its acceptance criteria and accepts it, at which point it is Published for the stated purpose, or rejects it for amendment.
Write down in the information standard what evidence each gate leaves behind: who checked, who authorised, who accepted and when. That record is what makes Archive useful later.
Work in progress
The task team is still producing the container. Other teams should not coordinate against it. Typical contents: an unchecked model, a drawing mid-edit, a schedule with placeholder codes. A preliminary calculation on this site can sit in a WIP note. It is not published design information.
Shared
The container is available so others can coordinate, comment or develop their own information. Shared does not mean accepted for construction, procurement or stage approval. Clash detection belongs here. Issue for construction does not.
Sharing is a permission change, not a quality certificate. A file can be Shared and still be wrong. Who may press the button, and what has to be true beforehand, belongs in the project’s agreed procedures rather than in individual habit.
Published
The container has been accepted for a stated purpose. That purpose might be a stage gate, a construction issue, or an asset handover pack. Published is not “the latest upload”. If the purpose is not written down, the state is only a folder name.
Archive
A record of a container that is no longer the live copy. Archive exists so a later dispute can see what was issued. It is not a second Shared folder with a tidier name. Do not federate against Archive and call the clash current.
State, revision, suitability
Three labels get collapsed in email. Keep them apart.
- State — where the container is allowed to be used. WIP, Shared, Published, Archive.
- Revision — which version of that container. The identity in the file name stays put. The revision metadata changes.
- Suitability — whether it is fit for a stated purpose. UK projects often keep those codes in the information standard, with one series used while information is still being coordinated and another once it has been authorised. This page does not reproduce those tables.
Moving a file to Shared does not approve it. Publishing it does not make a calculation on this site a design. The file-name checker does not read the state.
Worked sequence
EXAMPLE — drainage layout, one container name throughout.
- Civil task team draws it in WIP. Other disciplines cannot rely on it.
- It moves to Shared for the federated clash run. Comments come back. Suitability metadata says it is fit for coordination, not for construction.
- A revised container is Shared again. Same file name. New revision metadata.
- The revision accepted for construction is Published, for that purpose only.
- When the next accepted revision replaces it, the old Published file moves to Archive. It is not deleted, and it is not left in Shared “just in case”.
Where this goes wrong: a coordination-only drawing from Shared is printed and handed to the site gang. Nothing in the file name changed, so nobody noticed that it skipped both the authorisation and the acceptance gates.
What to write in the information standard
- Who may move a container between states.
- What check is required before Shared, and what acceptance is required before Published.
- Which suitability codes the project will actually use, and that they are metadata.
- That Archive is the record of what was issued, not a working area.
Common mistakes with suitability
A frequent error is sharing a container with a suitability that promises more than it should. A structural model shared “for coordination” is fine for clash checking; the same model labelled as suitable for construction while still in Shared tells the site something untrue. Another is changing the suitability without a new revision, so two different meanings point at the same file. The UK BIM Framework guidance lists the status codes used on UK projects; agree them in the information standard and use them exactly.
Questions
Can a container go back from Shared to Work in progress?
The shared version stays where it is as a record. The task team develops the next revision in Work in progress and shares it again when it is ready.
Who can publish?
Publishing follows authorisation by the lead appointed party and acceptance by the appointing party. A task team cannot publish its own work on its own authority.
What happens to Archive?
Archived containers are kept as a record of what was shared and published, and when. They are not deleted, so the history of decisions can be traced.
Do states apply to email attachments?
No. Information sent by email has left the CDE. If it is used for a decision, the container should be in the CDE with the right state and suitability, so the record is complete.
Is Published the end of the road?
No. Published information can be revised. A new revision is produced in Work in progress, shared, authorised and accepted, and then replaces the earlier one, which moves to Archive.
Related: File naming that survives federation · File-name checker · What a CDE is · Information requirements · ISO 19650 overview · Glossary
Sources
- BS EN ISO 19650-1:2018 and BS EN ISO 19650-2:2018, with the UK National Annex revised in 2021
- UK BIM Framework guidance
Last checked 19 October 2026. Gate names follow the ISO 19650 CDE workflow (check, review and approve; review and authorise; review and accept). Suitability code tables stay with the UK BIM Framework and the project information standard. Original guidance, not a design sign-off.