Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.
Project document control procedure
Without a written procedure, each discipline invents its own way of numbering, issuing and filing, and the differences surface at handover when nobody can say which set is the record. A short procedure that names the register, the numbering key, the revision rules, the transmittal route and who may issue a document gives the whole team one rulebook from the first issue.
First tasks
- Search the contract and client specifications for every clause on documents and drawings
- Draft the procedure outline with numbering, revisions, transmittals and archive sections
- Agree the originator, checker and approver roles with the discipline leads
- Issue the approved procedure to the project team under its own document number
- Review the procedure against lessons learned and client feedback @recurring(yearly)
Document numbering system with a worked key
Every document number should tell anyone the project, area or unit, discipline, document type and a sequence, so that a drawing found on a site office wall can be traced to the register in seconds. Fixing the field order, separators and code lists before the first document is raised avoids the renumbering campaigns that follow when two disciplines pick the same sequence.
First tasks
- Check whether the client specification prescribes a numbering format
- Define each number field with its length and allowed codes
- Write three example numbers and decode them field by field in the key
- Set the rule for who allocates sequence numbers from the register
Revision and status code scheme
Teams that let letters and numbers drift end up with a drawing at revision C on one sheet and revision 0 on the next, and nobody can tell which was issued for construction. A scheme that reserves letters for pre-construction issues, numbers from zero for issued for construction, and status codes such as IFR, IFA, IFC and AB makes the state of every document readable from its title block.
First tasks
- Collect the revision schemes used on your last two projects and the client's preference
- Write the table of revision sequences and status codes with their meanings
- State what a recipient may and may not do under each status code
- Send the agreed table to whoever maintains the drawing and document templates