Simple Document System For Projects

First Published:

Last Updated:

How long would it take someone new to your project to find the current cost forecast?

Would they open the project page and see a clearly labelled link? Or would they need to ask someone which drive to use, work through several folders, and then choose between three spreadsheets with almost the same name?

Now imagine the person who normally explains all this is on leave.

It is a small test, but it can tell you a lot about how much time your project team spends looking for information.

Problem: The Document System Makes Everyday Work Difficult

Too many places to look

Project information can end up spread across shared drives, document libraries, email attachments, individual computers and project management software. Each location may have a reasonable purpose, but the team still needs to know where to go.

Sometimes the difficulty is within one system. A file is buried in folders within folders, and finding it depends on remembering who created it or which stage the project was in at the time.

Folders are useful. The problem is making people navigate a complicated structure for something they need every day. Removing all folders and putting thousands of files into one unorganised list would be just as frustrating.

When finding a file takes too long, people keep their own copies. That seems helpful until several people are updating different copies and nobody knows which information to trust.

Small delays become a lot of wasted time

A slow system adds another problem. You find the document, click to open it, and wait. Saving or uploading it takes just as long.

Consider an illustrative example. If someone opens 40 files each working day and each takes an additional 30 seconds, that is 20 minutes a day. Across five days, it is one hour and 40 minutes per person. For 12 people, it adds up to 20 staff hours a week.

That calculation only counts the opening delay. It does not include searching, retrying failed connections or asking colleagues for help. The total lost time could be a lot more than most people realise. The actual disruption will depend on whether people can do useful work while waiting, but repeated delays still deserve attention.

Everyone develops their own workaround

If the approved change register is difficult to find or awkward to use, someone makes another spreadsheet. Someone else creates a different cost tracker. A third person stores important approvals in their email account.

The project manager then spends time collecting and comparing information that should already be available. Similar columns may even mean different things. One spreadsheet includes GST, another excludes it, and a third does not say.

These workarounds often tell you something useful. People are trying to get their work done, and the official system is making that difficult.

Buying more software will not automatically fix the problem. The organisation still needs to decide how the system will be arranged, who will maintain it and how people will learn to use it.

Solution: Make Project Documents Easy to Find and Use

Set up the system at the start

At the start of a project, take time to establish a simple document system. But do find out what the organisation already requires before creating a separate arrangement for your team.

Identify the documents people will use regularly, who needs access and where they will be working. Include people based at site, in client offices or in other locations. Their access may be quite different from yours.

Agree where the project keeps its working documents, issued documents, correspondence and records of decisions. Depending on the size of the project, you may need to give someone responsibility for maintaining the arrangement and resolving filing questions. Ideally that should be done across all your projects (i.e. make the process consistent).

Record the essentials in your project management plan. A short explanation with working links is more useful than pages of instructions that people cannot follow.

If you inherit a project, do this review early. You may need to improve the existing arrangement while keeping important records and links available.

Give the team a clear starting point

Provide one project page or index from which people can reach the information they commonly need. This could be part of an enterprise project management system, a document management system or a simple project home page.

Include clear links to the project plan, scope, schedule, cost records, registers, drawings and templates that the team uses. Group them in a way that makes sense to the people doing the work.

One starting point does not require every record to be stored in the same application. Your finance system may hold the accounting records while another system holds drawings. Explain the purpose of each and link to the right location.

For example, label a link “Current project forecast” rather than expecting people to know which spreadsheet contains it. Where practical, use a permanent document link that continues to work when the document is revised.

For an issued record that must preserve a particular revision, link or refer to that specific revision instead. A link that always opens the latest version serves a different purpose.

Use a consistent structure across projects

People moving between projects should recognise the basic filing arrangement. They should not need to learn a completely different system every time a project manager changes.

A small project might start with these main sections:

  • Project management and planning.
  • Scope and design.
  • Costs and procurement.
  • Correspondence and meetings.
  • Delivery and quality records.
  • Completion and handover.

These are examples to adapt to your organisation. Add subfolders where they make documents easier to find, but avoid creating empty levels simply because a large project once needed them.

Use the same names for the same things. If the organisation calls something a “variation register”, calling it a “change log” on another project may make it harder to find.

Where one document is relevant in several places, use shortcuts or links to the controlled source where the system allows it. Making several editable copies creates extra maintenance work and uncertainty.

Make search useful

People should be able to find a document by its title, document number or a relevant subject. Test those searches using terms that a new team member would actually enter.

Use clear document names. “P082 Pump Station Cost Forecast” tells the reader much more than “Updated spreadsheet”. Where dates are useful, use a consistent format, such as 2026-11-04, so they can be sorted sensibly.

The Western Australia Government’s guidance on document naming conventions provides useful background and some good examples on concise titles and consistent terminology.

If the system supports metadata, use a few helpful fields. Metadata simply means information about a document, such as its project, type or status. Make common values easy to select and avoid asking people to fill in fields that nobody uses.

Microsoft’s guide to custom views in a document library explains how columns, sorting, filtering and grouping can provide different ways to find documents in Sharepoint. A project could use that approach to show templates separately from completed records.

Test the result. A search that returns hundreds of irrelevant documents has not made the task easy.

Check speed and access where the team works

Test opening, editing, saving and uploading representative files from the locations where people will use them. Include larger drawings and spreadsheets, rather than testing only a short document from the main office.

If most of the team is in one city and the server is elsewhere, ask IT to check the connection and system performance. Depending on the arrangement, better connectivity, managed local caching or an approved cloud service may help, and could save a lot of wasted time.

Avoid solving slow access by encouraging everyone to maintain independent local copies. If offline access is necessary, establish how files are downloaded, updated and synchronised, and who resolves conflicting edits. A site team also needs to know which documents are available without an internet connection and how to check whether those copies are still current before use.

Check permissions at the same time. A contractor who needs to read an issued drawing may not need access to internal cost records. Give people the access their work requires, and make the process for requesting help clear.

Provide standard templates and registers

Make approved templates easy to reach from the project page. Start with the documents people commonly prepare, such as meeting minutes, cost forecasts, change requests and project reports.

For recurring records, agree on a standard register or system. Avoid having each person create a separate spreadsheet for the same information. Standard fields and definitions make it easier to combine information and understand another person’s work.

Keep the templates proportionate. A minor project should not have to complete irrelevant sections designed for a much larger project. Where different versions are justified, make their purpose clear and maintain them through the same central process.

My post on easy-to-find forms and templates covers the problems caused when people cannot locate the approved starting document.

Before releasing a template, ask the people who will use it to complete a realistic example. That often reveals unclear instructions, missing fields or unnecessary work more quickly than reviewing a blank form.

Avoid entering the same information repeatedly

A document system should help the team use information already recorded. Check whether a project report can draw from an existing register or whether an approved integration can provide the required figures.

For example, an approved variation may affect the variation register, forecast and monthly report. Decide where its approved value is maintained and how the other records receive it.

Be careful with spreadsheets that link to other files. Moving or renaming a source file can break the connection. Someone must understand the links, check the outputs and maintain them.

Where systems cannot be connected reliably, define who updates each record and when the figures are checked against each other. Make the remaining manual work visible so it is included in the project’s workload.

Also explain which source takes precedence when figures conflict. A forecast and an approved budget may legitimately differ, but you shouldn’t have two different conflicting approved budgets, one needs to supersede the other. Make it clear which one takes precedence. My post on clarifying who uses documents and why discusses these responsibilities and the purpose behind an update.

Train people through the tasks they need to do

Give every team member practical training. Sending a link to a procedure does not tell you whether they can actually find and save a file.

Ask a new user to locate a current document, find a template, save a new record and submit something for review. Let them try it using their own permissions. Explain how to capture project correspondence so important decisions remain available to the team.

Provide a short guide with links, a few examples and the name of someone who can help. Include this in the induction for people who join later, including temporary staff and contractors who use the system.

If several people struggle with the same task, review the arrangement. Training can explain a sensible system, but it should not become a substitute for fixing an unnecessarily difficult one.

Make improvements easy to request and manage

Anyone using the system should have a straightforward way to suggest an improvement. A confusing heading or missing field should not take weeks of approvals to resolve.

Give the responsible owner enough authority to assess routine improvements quickly. Changes affecting calculations, approval authority or contractual wording need review by the appropriate people, but simple corrections should not. Match the review to the effect of the change.

Publish the approved template centrally, identify the revision and tell users what has changed. Make clear whether existing project records need updating or whether the new template applies only to future documents.

Keep previous records where required. Simplifying the system is not a reason to delete evidence or remove necessary checks. The related discipline of project document control helps maintain reliable revisions and coordinated issue of documents.

Before handover, check that another person can find the key records and open the links. Confirm the organisation’s arrangements for continued access, backup and retention. Project information should remain usable after the original team has moved on, but it is amazing how many companies and projects muck this up.

Lesson: Make the Document System Easy to Use

A simple document system reduces the effort needed to find, save and use project information. Establish it early, make the structure familiar and check that it works from the places where your team actually works.

I would rather see a modest system that people understand and maintain than an elaborate one that encourages everyone to keep separate copies.

Give the team a clear starting point, useful templates and practical training. Keep the controls the project needs, and make routine improvements easy to manage.

Then try the test again. Ask someone new to find the current cost forecast without help. If they struggle, you have found something worth fixing.

Leave a comment