Released drawings and revisions
Part number, drawing number, revision and release status held as columns, with versioning and check-out behind them, so “which rev is current?” is answered by a view rather than by a file name.
SharePoint consulting for manufacturers
SharePoint for manufacturing: drawings, SOPs, approvals and a plant intranet in one place
A plant runs on released drawings, work instructions, engineering changes, safety notices and supplier paperwork — usually spread across a file server, an engineering share, a binder at each station and somebody’s inbox. SharePoint for manufacturing means configuring the Microsoft 365 you already license around that estate: one released set per part, SOPs nobody can open in draft, change approvals with a recorded decision, a plant intranet the floor actually reads, and supplier files that never touch the rest of the tenant. Quality-system and ISO 9001 builds are narrower engagements we route you to. One written fixed fee, typical delivery in 2–4 weeks, 30 days of hypercare included.
One fixed price, approved before work begins · 30 days of hypercare included
Sample dashboard. Illustrative data, not a client’s numbers
One fixed price, agreed before any work starts
You get a written proposal with one fixed price, clear deliverables and a timeline, and you approve it before anything starts. If the scope changes, the price changes in writing first, and every engagement includes 30 days of hypercare after handover.
What we configure
What does a SharePoint build for a plant include?
Six pieces cover most of a manufacturer’s document estate. Your scope takes the ones that match how the plant runs today — each is configuration of tools already inside your Microsoft 365 licenses.
SOPs and work instructions
A published library per area or line, with drafts hidden from readers until an approver releases them, owners and review dates as fields, and the same link working at the station after every revision.
Engineering change approvals
An ECN or ECO becomes one record carrying the affected parts, the reason, the redlines and the approvers, routed in sequence and written back with who approved it and when.
A plant intranet
Safety notices, shift news, the forms people actually need and the links to current SOPs on one home page per site, readable on a phone or a shared screen on the floor.
Supplier document exchange
Certificates of conformance, material certs, first-article packages and the drawings you issue to a supplier, exchanged through a site that admits named guests and nothing else.
Search by part, not by memory
Part number, customer, line and document type as managed metadata, so the setup sheet for a part last run two years ago is findable by someone who was not on that shift.
Want those six pieces mapped onto your own plant? A senior engineer will walk through it with you, at no cost.
Talk it through →How it works
How does a plant build run from first call to hypercare?
- 1
Follow one part through the plant
A free consultation traces a real part: where its drawing is released, how a change is raised and approved, which SOP the operator opens, what the supplier receives and where the floor hears about a safety issue. We reply with a written scope, one fixed fee and a delivery date.
- 2
Build one line or one product family as the pilot
We configure the drawing and SOP libraries, the metadata, the change approval route and the permission model, then run one line or product family on it — including one supplier — before any of it becomes the standard.
- 3
Roll out area by area, then retire the share
Remaining areas move in waves with metadata applied on the way, the plant intranet goes live, document owners and approvers are trained, and we stay on for 30 days of included hypercare.
Why does a plant’s file share stop working?
Because a folder is a location, not a record. It cannot carry a revision, a release status, an approver or a review date, and nothing stops a copy of last year’s work instruction living in three folders. The share works while one engineer remembers where things are, and fails the first time an operator builds to an old revision.
The pattern is close to identical at every small and mid-sized manufacturer. There is an engineering share with a folder per customer or part family, a “Released” folder containing several revisions and a subfolder called “OLD”, printed work instructions in a binder at each station that nobody is sure match the file, change requests that live in email threads, and supplier certificates saved wherever the buyer happened to be when they arrived. None of that is a discipline problem. The work is turning the things a plant already talks about — the part, the released drawing, the SOP, the change, the supplier — into objects the platform understands, so the answer comes from the system instead of from the person who set the folder up.
Which plant documents belong where in SharePoint?
Each document type gets a home matched to how it changes and who must see it. Released drawings and SOPs need revision control and a published view; change requests need an approval route; safety notices need reach; supplier files need an external boundary. The table is the map we scope against, including what we route to a narrower build.
| What the plant calls it | What it becomes in SharePoint | Why the folder version cannot do it |
|---|---|---|
| Released drawing | A library with part number, drawing number, revision and release status as columns, versioning on, check-out required, and a view showing only the released revision | “Rev D final(2).pdf” is a file name, not a revision record, and nothing stops a copy of it sitting in another folder |
| SOP or work instruction | A published library per area with content approval, so drafts stay hidden from operators, plus owner and next-review-date fields | A shared folder shows everyone every draft, and a binder at the station has no way to know it was superseded |
| ECN / ECO | A list item or document set per change holding the affected parts, reason, redlines and approvals, routed by a flow and written back with the decision | An email thread has no number, no status and no record of who approved which revision |
| Safety notice and shift news | News posts on a plant intranet home page, targeted per site, with the current SOPs and forms one tap away | A notice in a folder is read by nobody; one taped to the break-room wall cannot be updated or confirmed |
| Supplier certificates and first-article packages | A supplier site with a library per supplier, named guest access, and metadata for part, lot and certificate type | Email attachments have no revocation, no expiry and no record of who opened what |
| Nonconformance, CAPA, internal audit | Routed to our SharePoint quality management system build, which weighs SharePoint against a licensed QMS before anything is configured | These are workflows with owners and due dates, not documents, and deserve their own scope |
| Audited controlled-document set | Routed to our SharePoint ISO 9001 document control build: register, acknowledgement records and evidence export | An auditor tests behaviours a general library does not have until they are deliberately built |
Recognize your own share in the right-hand column? Tell us how it is laid out and we’ll send a written scope with one fixed price.
Scope my project →How do drawings and SOPs stay current on the shop floor?
Through versioning, content approval and a single published link. Revision lives in a column so a view shows only what is released, drafts are hidden from operators until an approver publishes them, check-out stops two engineers overwriting the same file, and the link at the station always opens the current revision rather than a saved copy.
Version history needs deliberate settings, not defaults. Microsoft’s documentation on version history limits for document libraries (opens in new tab) explains that limits can be set at organization, site or library level, and that versions trimmed past a limit are permanently deleted without passing through the recycle bin. For a drawing library where a superseded revision may be needed years later, that is a real decision, and we make it explicitly in the scope. Content approval and draft visibility are set per library, as Microsoft describes in its guidance on enabling and configuring versioning (opens in new tab).
One honest boundary: CAD models do not co-author the way a Word document does, and SharePoint is not a CAD vault. Where you already run a PDM or PLM system, it stays the system of record for models and bills of materials, and SharePoint holds the released PDFs, the SOPs and everything else around them. Where you have neither, released PDFs in a controlled library are usually a large step up from a share.
How does an engineering change get approved without email?
A change request becomes one record with the affected parts, the reason and the redlines attached, and a Power Automate flow routes it to engineering, quality and production in the order you set. Each decision, approver and timestamp is written back to the record, so the history of a revision is a filter rather than an inbox search.
The mechanism is Microsoft’s standard approval action. Its approval workflow documentation (opens in new tab) covers single approvers, first-to-respond, everyone-must-approve and sequential stages — which is how a change goes to the design engineer before the quality manager and production sign-off. Two design rules decide whether it survives staffing changes: the flow’s connections are owned by a service account rather than a person who might leave, and every approval step has a named deputy. Our guide to building an approval workflow in Power Automate walks through the same mechanics for spend and requests, and larger routing work belongs with our Power Automate consulting.
What goes on a plant intranet, and who reads it?
A plant intranet is the front door for people who do not sit at a desk: safety notices and shift news at the top, links to current SOPs and forms for their area, and the contacts they need. It works when it is short, readable on a phone or a shared screen, and owned by someone at the plant.
The limit is accounts, not pages. Operators who sign in on a phone, tablet or shared kiosk can read the intranet and the SOP libraries; staff with no Microsoft 365 account cannot, and no amount of page design changes that. We check who holds which license during scoping and tell you plainly what the floor can reach before anything is built. Where the plant needs to capture data rather than read it — inspections, downtime reasons, checklists — that is an app, and it belongs with our Power Apps consulting rather than with SharePoint pages.
How do suppliers exchange documents without seeing the rest of the tenant?
Through a supplier site that allows named guests while every other site stays internal. Each supplier signs in under its own identity, sees only its own library, uploads certificates and first-article packages there, and receives the drawings you issue to it. Access ends when you remove it, and the audit log records who opened what.
Microsoft’s external sharing documentation (opens in new tab) sets out the model: sharing is controlled at the organization level and then per site, and a site can never be more permissive than the tenant. We set the guardrails at the same time — link defaults that do not silently create anonymous links, expiry on guest access, and a short list of which sites may share externally at all. Defense suppliers handling export-controlled or controlled unclassified information face tenant requirements this build does not address; we raise that in the consultation rather than guess.
When should a manufacturer buy the QMS or ISO 9001 build instead?
When the problem is the quality system rather than the plant’s files. If nonconformance, CAPA and internal audits are the pain, the quality management system build is the right scope. If an auditor found obsolete documents in circulation, ISO 9001 document control is. If files are simply everywhere, this broader build comes first and the others follow.
This page is the plant-wide hub. The SharePoint quality management system comparison weighs a native SharePoint build against a licensed QMS product, a dedicated eQMS and a custom build, module by module. The SharePoint ISO 9001 document control engagement is narrower and stricter: it turns the documented-information clause your quality manual already commits to into a controlled library with a register, acknowledgement records and evidence that exports. Neither makes you certified — we are not a quality consultancy or a registrar — but both start far more cheaply on top of a document estate that is already organized.
Reporting is a separate service line again. Once parts, changes and nonconformances carry real metadata, OEE, downtime, scrap and on-time-delivery dashboards are what our Power BI consultant for manufacturing engagement builds. And where the plant’s files still sit on a server, our file server to SharePoint migration playbook explains why the structure is designed before anything moves. Manufacturers that run their own warehouses or fleet can see the freight-side equivalent in our guide to SharePoint for logistics companies.
What does the engagement cover?
Three shapes cover most requests from manufacturers. Every fee is fixed and put in writing after your free consultation — the table shows scope and typical timeline, because an honest number needs to see your document types, your current share and your license position first. Our fixed-fee process explains how the number is set.
| Engagement | What is configured | Typical timeline | Fee |
|---|---|---|---|
| Drawing and SOP control foundation | Released drawing and SOP libraries with versioning, check-out and content approval, part and document-type metadata, published views, owner documentation, and one line or product family as the pilot | About 2 weeks | Fixed fee — scoped after your free consultation |
| Change approvals and supplier exchange | The above plus the ECN/ECO record and approval route, deputies and service-account ownership, the supplier site with guest access and certificate metadata, and sharing guardrails | 2–3 weeks | Fixed fee — scoped after your free consultation |
| Plant-wide rollout | The plant intranet with safety news and per-area SOP links, migration of agreed content off the file server with metadata applied in flight, retention settings for superseded revisions, training for owners and approvers, and admin runbooks | 3–4 weeks | Fixed fee — scoped after your free consultation |
Whatever the shape, you own everything: the libraries, the flows, the metadata, the intranet and the documentation stay in your Microsoft tenant from the first day, and nothing we build depends on us to keep running.
Which manufacturers is this a good fit for?
Manufacturers of 20 to 500 people, paying for Microsoft 365, running the plant off a file server or shared folders. The usual trigger is a part built to an old revision, a customer asking for evidence of change control, a server refresh quote, or a new operations lead who will not accept “it’s on the S: drive”.
It fits badly when part numbering or the revision scheme is still undecided, because structure built on an undecided convention gets rebuilt; settle the convention first, then call us. Multi-plant groups with a corporate PLM program usually need a larger integration partner than a fixed-fee build. This page is the manufacturing-shaped version of our wider SharePoint intranet and document management consulting — same engineering standards, plant vocabulary. We work with manufacturers in all US states remotely from our Orange County, CA base.
Sound like your plant? Tell us where the files live today and a senior engineer will reply within one business day.
Book my free consultation →Fair and square
Our promises, in plain English
One fixed price, approved before work begins
Every project gets a written proposal with one fixed price for a defined scope, and you approve it before any work starts. No hourly meter and no retainer. If the scope changes, the price changes in writing first.
You own everything, in your tenant
Reports, apps, flows, sites and documentation are built in your Microsoft tenant, under your accounts. There is no proprietary layer and no ongoing license owed to us, so nothing breaks if you never hire us again.
30 days of hypercare, included
For 30 days after handover we fix defects in what we delivered, answer your team’s questions and make small adjustments that keep it working as scoped, at no extra cost.
The engineer who scopes it builds it
A senior, US-based engineer works with you from the first call to the handover. There is no junior bench and no offshore handoff.
Straight answers. The free consultation ends with either a fixed-fee proposal or an honest recommendation that we are not the right fit.
Talk to an engineer, not a sales rep. Microsoft Made Easy is a Lightray Solutions brand, founded by Edward Pinela and headquartered in Orange County, California. Senior engineers across the Microsoft stack deliver fixed-fee projects for companies in every US state, remotely. About us
FAQ
Questions manufacturers ask before scoping
Usually not, and we will say so. If you need CAD vault check-in tied to the modeling tool, bills of materials and where-used queries, keep the PDM or PLM. SharePoint fits the released PDFs, SOPs, change paperwork, supplier files and everything the engineering vault was never meant to hold.
Content approval keeps drafts visible only to authors and approvers, so operators open the published revision and nothing else. The link on the station tablet or intranet page points at the document, not a copy, so when a new revision publishes the same link opens it. Superseded revisions stay in history rather than circulating.
If the trigger is an audit finding about obsolete documents, start with ISO 9001 document control. If nonconformance, CAPA, internal audits and supplier approval also live in spreadsheets, look at the full quality management system build. If the problem is simply that plant files are everywhere, this broader manufacturing build comes first.
Yes. External sharing is set per site, so a supplier site can admit named guests while the rest of the tenant stays internal. Each supplier signs in under its own identity, sees only its own library, and access ends the day you remove it, not whenever a forwarded link happens to expire.
Usually, but it depends on accounts, not on SharePoint. Operators who sign in on a phone, tablet or shared kiosk can read SOPs and the plant intranet. Staff with no Microsoft 365 account cannot. We check who has which license during scoping and tell you plainly what the plant floor can reach.
Typical delivery is two to four weeks from kickoff, with the date in your written scope. The fixed fee follows how many document types you control, how many change-approval routes differ, whether suppliers get external access, whether a plant intranet is in scope, and how much content moves off the file server.
Get your plant’s document estate scoped in writing
No hourly meter and no retainer. A senior US-based engineer talks it through with you first, at no cost; you approve one fixed price, and the engineer who scoped it does the work.
One fixed price, approved before work begins · 30 days of hypercare included
Tell us what you’re trying to fix — a report, an approval process, an intranet, a Copilot rollout. We scope it as a fixed-fee project, you approve, and a senior engineer delivers in 2–4 weeks.
- Fixed-fee scope agreed before any work starts
- Senior, US-based Microsoft engineers — no handoffs
- Typical 2–4 week delivery
- 30 days of post-delivery hypercare included
Related services
What manufacturers usually scope alongside this
SharePoint Quality Management System
Nonconformance, CAPA, internal audits and supplier qualification, weighed against a licensed QMS before anything is built.
ISO 9001 Document Control
A controlled library with a register, approval evidence and acknowledgement records that holds up at an external audit.
Power BI for Manufacturing
OEE, downtime, scrap and on-time-delivery reporting, built on the data your plant already produces.