Shop Drawing Workflow Automation
Budget / Salary750–1,500 SGD
TypeFreelance project
LocationRemote
Posted2 hours ago
I need a SharePoint Online document library and a set of Power Automate flows that take every shop-drawing PDF my team uploads and push it through a complete internal review and approval cycle. The drawings are strictly for internal review and approval, never client-facing, so the workflow must reflect that.
Here is what has to happen to each file:
1. As soon as a drawing lands in the library (drag-and-drop or email-in), the flow must pick up the file name, parse the drawing number, revision, and title, and write those fields into library columns while also adding the file to an automatically generated “Drawing List” (Excel or SharePoint List—open to suggestions).
2. The flow then routes the drawing to our predefined approvers in sequence. Each approver receives an Outlook notification with the drawing attached and a link to approve or reject inside SharePoint. Rejections restart the loop to the submitter with comments; approvals move to the next reviewer until final sign-off.
3. Status updates (submitted, in review, approved, rejected, archived) must hit the original submitter’s inbox and appear in Teams notifications so nobody misses a step.
4. Once final approval is logged, the file is automatically copied to a read-only “Approved Drawings” library (our archive) with version history intact, leaving the working copy where it is but clearly marked as “Archived”.
5. Whenever a new revision of the same drawing is uploaded, the system should supersede the old version, increment the revision field, and keep the prior revision in the archive.
Acceptance criteria
• Filename metadata is parsed accurately into separate columns 100% of the time.
• Approval routing, notifications, and status updates fire within one minute of any trigger event.
• Drawings appear in the “Drawing List” with live links and correct metadata.
• Final files are archived to the designated library with the correct retention label.
If you have experience building similar SharePoint + Power Automate document control solutions, let’s set this up so my engineers can focus on design work instead of chasing paper.
Here is what has to happen to each file:
1. As soon as a drawing lands in the library (drag-and-drop or email-in), the flow must pick up the file name, parse the drawing number, revision, and title, and write those fields into library columns while also adding the file to an automatically generated “Drawing List” (Excel or SharePoint List—open to suggestions).
2. The flow then routes the drawing to our predefined approvers in sequence. Each approver receives an Outlook notification with the drawing attached and a link to approve or reject inside SharePoint. Rejections restart the loop to the submitter with comments; approvals move to the next reviewer until final sign-off.
3. Status updates (submitted, in review, approved, rejected, archived) must hit the original submitter’s inbox and appear in Teams notifications so nobody misses a step.
4. Once final approval is logged, the file is automatically copied to a read-only “Approved Drawings” library (our archive) with version history intact, leaving the working copy where it is but clearly marked as “Archived”.
5. Whenever a new revision of the same drawing is uploaded, the system should supersede the old version, increment the revision field, and keep the prior revision in the archive.
Acceptance criteria
• Filename metadata is parsed accurately into separate columns 100% of the time.
• Approval routing, notifications, and status updates fire within one minute of any trigger event.
• Drawings appear in the “Drawing List” with live links and correct metadata.
• Final files are archived to the designated library with the correct retention label.
If you have experience building similar SharePoint + Power Automate document control solutions, let’s set this up so my engineers can focus on design work instead of chasing paper.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.