ISO 19650 status codes - also called suitability codes - say what a file can be used for right now. They stop a model that's still work in progress being used to order steel. Here is the full list from the UK National Annex to ISO 19650-2, with what each code means in practice.
Status codes for work in progress and shared information
| Code | Meaning | In practice |
|---|---|---|
| S0 | Initial status | Work in progress, in the task team's own area of the CDE |
| S1 | Suitable for coordination | Shared so other teams can coordinate against it |
| S2 | Suitable for information | Shared for reference only |
| S3 | Suitable for review and comment | Shared for others to review |
| S4 | Suitable for stage approval | Ready for the appointing party to approve at a stage |
| S5 | Withdrawn | No longer used in later editions; check your information standard |
| S6 | Suitable for PIM authorisation | Project information model ready to be authorised |
| S7 | Suitable for AIM authorisation | Asset information model ready to be authorised |
Status codes for published information
| Code | Meaning |
|---|---|
| A1, A2, A3... | Authorised and accepted at a stage (the number is the stage) |
| B1, B2, B3... | Partially authorised and accepted, with comments to address |
| CR | As constructed record |
Revision codes
Revisions run alongside the status. While information is preliminary it's P01, P02..., with versions such as P01.1 while it's still work in progress. Once it's contractual it becomes C01, C02.... The status says what the file is fit for; the revision says which issue it is.
How status codes move a file through the CDE
- Work in progress (S0) - only the task team sees it.
- Shared (S1-S4) - checked and approved by the task team, then visible to the delivery team.
- Published (A, B, CR) - authorised by the lead appointed party and accepted by the appointing party.
- Archived - kept as the record of what was shared and when.
Where teams go wrong
- Sharing at S0. If another team can see it, it isn't work in progress any more.
- Treating S2 as approved. "For information" means "don't build from this".
- Codes in the file name. Keep status and revision as information on the CDE, so the file name never changes.
In Plannerly, each deliverable in your MIDP becomes a named file request. Connect Autodesk Construction Cloud or BIM 360, and a file shared there with a matching name fills its request by itself, so the plan shows what has arrived and which team owns the rest (how CDE Connect works).
