Home/Process library/From working copy to approved drawing
Process library · EngineeringFrom working copy to approved drawing
The engineer keeps working in the working copy. When a revision is ready, M-Files publishes it as a PDF with the next revision letter, sends it to the checker named on the drawing, and asks the approver for an electronic signature.
In short
In this blueprint an engineering firm keeps two records per drawing in M-Files: a working copy with the source file, and release copies for every revision. The engineer creates the drawing as a working copy in draft, linked to its placeholder and master document list; the name follows the naming convention. The reviewer and approver are filled in on the drawing, and the workflow sends its tasks to exactly those people. Moving the working copy to review publishes a release copy with the next revision letter, converted to PDF. The checker gets a review task; rejecting it sends the drawing back, completing it moves it to approval. The approver approves with an electronic signature, and the document status becomes OK. Every version stays in the history. SoftAdvice built and documented the process.
Which revision is the approved one?
A drawing is sent to the client. It turns out to be revision A. Revision B was approved last week.
A drawing changes many times before it is approved, and again after. Engineers need the source file to keep working; everyone else needs the approved PDF, with its revision letter.
When both live in the same folder, a draft is sent as if it were approved, and nobody can show who checked revision B.
- Working copy and release copies apart
- Revision letters set by the system
- Checker and approver named on the drawing
- Approval with an electronic signature
What happens from the first sketch to an approved revision
The working copy moves at the pace of the engineer. Each revision moves at the pace of the review.
While drafting
Work and comment
Versions, annotations, comments with colleagues tagged, track changes in Office.
When a revision is ready
Release
A release copy with the next revision letter and a PDF.
Within days
Check
The checker reviews the PDF and accepts or rejects.
At approval
Sign
The approver signs electronically; the status becomes OK.
From working copy to approved revision, step by step
People check and approve. M-Files numbers, converts, routes and records every step in the history.
Create the working copy
The engineer adds the drawing as a working copy, linked to its placeholder and master document list. It starts in draft and gets its name from the naming convention; mistakes in the metadata can still be fixed.
Name the reviewers
The checker and approver are filled in on the drawing. The workflow sends its tasks to exactly these people, so changing a name changes the route.
Release a revision
Moving the working copy to review publishes a release copy with the next revision letter, converted to PDF. The source file stays in the working copy.
Check
The checker gets a review task with a notification. Completing it moves the drawing to approval; rejecting it sends it back.
Approve and sign
The approver approves with an electronic signature. The document status becomes OK, and the revision is the one everyone uses.
Two records per drawing
The working copy keeps the source and the versions. Each release copy is one revision, with its PDF, its review and its signature.
Working copy
Release copy
From guessing the revision to knowing it
Engineers keep working in one file, and everyone else sees only approved, numbered PDFs.
Before
- Drafts and approved drawings in one folder
- Revision letters typed by hand
- Review requested by mail
- No proof of who approved
Now
- Working copy and release copies apart
- Next revision letter by the system
- Tasks for the people named on the drawing
- Approval signed electronically
M-Files and the SoftAdvice Engineering Pack
Configured and documented by SoftAdvice.
Revisions and version control
Every save is a version; every release is a revision with its own letter and PDF.
Review with electronic signature
Tasks for the people named on the document, and a signature at approval.
Questions about this blueprint
Why a working copy and a release copy?
So the engineer can keep working in the source file while a revision is in review. The release copy holds the PDF that is checked, approved and shared.
Is the electronic signature legally binding?
The approval signature records who approved and when, inside M-Files. For a legal signature towards the client, the transmittal that sends the documents is signed with an e-signature service.
Can the client see drawings in review?
No. A drawing in review is not shared. Only approved revisions go to the client.
Who approved your last revision?
In a one-hour demo we take a drawing from working copy to an approved, signed revision.
