Home/Process library/From master document list to project overview
Process library · EngineeringFrom master document list to project overview
Every project starts with a list of what it will produce, what the client sends and what suppliers deliver. In M-Files those lists are not spreadsheets: each line is a document with a status, and the project overview shows them all.
See the flow Deliverables management
In short
In this blueprint an engineering firm plans the documents of each project in master document lists (MDL) in M-Files: one internal list, one for what the client sends and one for what suppliers deliver. Every expected document is a placeholder, linked to its list and to the work breakdown structure. Documents the client must send wait open for upload. As engineers work, each document carries a status that follows its workflow: in progress, in review, OK or not OK. The project overview shows one row per list with the status of key documents such as the kick-off meeting, the project management plan and the drawings, and views filter progress per document type, list, project or work package. SoftAdvice built and documented the process.
Three lists, and none of them up to date
Progress meeting tomorrow. The client asks for the document list. Someone spends the evening updating a spreadsheet.
An engineering project lives on a master document list: what the firm will deliver, what the client must send and what suppliers must provide. The client asks for it at every progress meeting.
Kept in a spreadsheet, the list is out of date the day after the meeting. The real status sits in the documents themselves, scattered over folders and mailboxes.
- Internal, client and supplier lists
- Every expected document as a placeholder
- Status taken from the workflow, not typed
- One overview per project
What happens from kick-off to every progress meeting
The list is made once and then keeps itself current, because it is made of the documents.
At the start
Create the project
Name, number and client, and the three master document lists.
At kick-off
Plan the documents
Every expected document gets a placeholder on its list and in the work breakdown.
Every day
Work and review
Engineers fill the placeholders; the status follows the workflow.
At every progress meeting
Show the overview
One row per list, the status of every key document, filtered as the client asks.
From new project to live overview, step by step
The project manager plans, engineers produce, and the status is recorded in the history of every document.
Create the project
The project manager creates the project with its name, number and client. It appears in the list of all projects.
Plan in three lists
Each project has an internal master document list, a client list and a supplier list. Every document is linked to its list and to the work breakdown levels.
Reserve with placeholders
Every expected document is a placeholder from a template. A document the client must send starts open for upload.
Produce
Engineers add their document to the placeholder; it keeps its list, project and work package.
Status from the workflow
As the document moves through its workflow, its status follows: in progress, in review, OK or not OK. Nobody types it.
Follow up
The project overview shows one row per list with the status of key documents; views filter per document type, list, project or work package.
Four statuses, read from the workflow
The status on the list is the status of the document itself, so the overview is never behind.
Document on the list
From updating the list to reading it
The project manager walks into the progress meeting with an overview that is as current as the documents.
Before
- Lists kept in spreadsheets
- Status typed by hand
- Client documents arrive by mail
- Progress rebuilt before every meeting
Now
- Every line is a document
- Status follows the workflow
- Client documents wait open for upload
- One overview per project
M-Files and the SoftAdvice Engineering Pack
Configured and documented by SoftAdvice.
Master document lists
Internal, client and supplier lists per project, with every document linked to its list and work package.
Project overview
One row per list with the status of key documents, and views per type, list, project or work package.
Questions about this blueprint
Why three lists per project?
Because what you produce, what the client sends and what suppliers deliver are followed by different people and on different terms. Each list can be filtered and shared on its own.
Can we export the list for the client?
Yes. Any view can be exported to Excel. A report or dashboard with figures per status can be added on top.
Do we have to fill in the status?
No. The status follows the workflow of the document, so it changes when the document moves.
What does your next progress meeting look like?
In a one-hour demo we follow one project from its master document lists to the overview.
