60 mins
Easy
Any
The aim is to agree on what document statuses should be used and when. Having more choices is almost always a bad idea and means people are more likely to make the wrong choice.
Keep it simple and make sure you are managing project documentation clearly and consistently.
Get you off to the right start and help you decide what statuses you need and how to get them set up.
Inefficient collaboration and misunderstandings as to what documents can be used. These are signs of poorly managed documentation and in particular, the status assigned to documents.
Teams often spend a lot of time looking for the documents they need. It's not unusual to have trouble finding the latest versions or realize that the team might be using old documents that then create more work or worse, rework.
You'll need different stakeholders involved to get a holistic picture of what statuses are required. Typically, you'll need to understand the requirements of:
1. People creating and distributing documents (e.g. Consultants and Subcontractors)
2. People reviewing documents (e.g. Consultants and Contractors)
3. People managing documents (e.g. Document Controllers)
But, be mindful of having too many opinions. Groups of 4-5 tend to work best. More people means more discussion and fewer decisions. You can get feedback on decisions made with a wider audience later on.
Before you get people together, start by checking if there are any contractual, legal or regulatory requirements regarding how you and the greater project team are required to manage project related documents. This can help decide on the statuses you might need which makes this play easier.
Also think about previous experiences. What worked, what didn't? What caused confusion within the team? Try not to repeat earlier mistakes.
Making sure everyone is on the same page.
Start by watching this video that provides a simple overview of document statuses as they relate to project roles. It'll help the group get on the same page and better understand what decisions need to be made.
Then spend about 5 mins to get everyone to write down what their initial thoughts are on the statuses they want to see on the project. At this stage anything goes. It can be a big list but it's just an initial take on what you and your team think is needed. You'll reduce it in subsequent steps.
Here's where you'll get into deeper discussions.
You need to decide what statuses are needed on your project and/or within your team.
A good starting point for discussion is to have the following reasons covered with a specific status as a minimum:
1. Documents required but not created yet (e.g. placeholders)
2. Documents being worked on that can be used for information/discussions
3. Documents ready to be reviewed
4. Documents ready for use (i.e. for construction)
Spend a maximum of 5 mins on each one. You'll probably end up with many options for each one. Decide on your preferred status for each one but keep the others on the list for now.
Time to make that list more manageable.
Okay. You should now have a list of document statuses that you think would be useful. Now you need to make sure there is no room for confusion or ambiguity. That will often result in delays and mistakes.
Go through the list with the group and decide if there are any statuses that could be confused with each other. For example, if you have DRAFT and PRELIMINARY, they could be confused as serving the same purpose. So why would you need both?
Can you have what you want?
There are lots of document statuses available in Aconex, but every now and then, an unusual one comes up. It's worth double checking that all the statuses you need are actually available for use.
Follow these instructions to browse the list of available Document statuses.
Use the search option to quickly look for the one you're after.
If the document status you want is not available, you'll need to find an alternative. If you really do need to use a status that's not available, then follow these instructions.
Finally, confirm the final list of document statuses.
That's the end of the Play.
Now it's time to get everything set up.
Now you've done the hard work, it's time to document it. Yes, we know that's not very interesting, but if nothing's documented, then the project team can easily claim ignorance when it comes to what statuses they should be using.
Here's a table showing what it might look like:
| Document Status & Description of Use | CL | PM | CN | MC | SC |
|---|---|---|---|---|---|
As-BuiltFor documents which reflect ‘as-constructed’ or ‘as-built’ information. |
no
|
no
|
yes
|
yes
|
yes
|
DraftFor documents to be issued for initial review or that are currently in progress. |
yes
|
yes
|
yes
|
yes
|
yes
|
FinalDocuments that are deemed to be final and do not necessarily require review (e.g. not drawings). |
no
|
no
|
yes
|
yes
|
yes
|
For ApprovalFor documents that required to be formerly approved and signed off. |
yes
|
yes
|
yes
|
yes
|
no
|
For ConstructionFor documents which are for construction purposes. |
no
|
yes
|
yes
|
yes
|
no
|
For DesignFor all design documentation. |
yes
|
yes
|
yes
|
yes
|
no
|
For InformationFor documents that are issued for information only. |
yes
|
yes
|
yes
|
yes
|
yes
|
For ReviewFor documents that are required to be reviewed (e.g. at different project phases). |
no
|
no
|
yes
|
yes
|
yes
|
For TenderFor documents which are for tender or bid purposes. |
no
|
yes
|
yes
|
yes
|
yes
|
Not StartedDocuments that have not yet been started or are being prepared (e.g. placeholder documents). |
yes
|
yes
|
yes
|
yes
|
yes
|
RejectedDocuments that require changes or updates before they can be used. |
yes
|
yes
|
yes
|
yes
|
yes
|
This list is a good set of Document statuses and will provide clarity and ease of reporting. That's what you should aim for.
Follow the steps to get your project configured with the agreed document statuses.
Note: You will need to be a Project Admin to add and assign document statuses.
1. Add the relevant document statuses to the relevant roles.
2. Then, assign the role to the organizations or companies that need to use the specific document statuses.
3. If you need to create a new role, follow these instructions and then add the relevant statuses to the new role.
It's always a good idea to double-check everything and make sure each role has the right statuses assigned.
That's it! You've now decided what document statuses are important for you and your team, and set them up in Aconex.