Staging with a valid-from date
If the valid-from date is in the future, the approved version goes into distribution. A nightly run switches over on the effective date. Until then, a version can also be withdrawn again.
Document control for Microsoft 365
Smarter DMS
Control your governing documents, from editing to archive.
Smarter DMS maps the lifecycle of your work instructions, procedures and policies in SharePoint: editing, review and approval, distribution ahead of the effective date, the valid version, archive. The core is proven in customer projects. Roles, stages and deadlines are aligned with your process.
- from IMS, QMS and rulebooks
- 5 real examples
- documents stay in your tenant
- Your SharePoint
The problem
Why major and minor versions are not enough
A work instruction is revised in November and applies from the turn of the year. Until then, the current version has to remain valid. At the same time, everyone affected should already be able to read and confirm the new one.
SharePoint only knows two states for this: draft or published. Once the new major version is published, it immediately replaces the previous one for readers. If it stays a draft, only editors can see it. An approved version that applies from a future date is not part of the standard.
- Two versions visible at the same time: the valid one and the upcoming one
- Acknowledgement before the effective date, tied to the upcoming version
- Switch-over in the night before the valid-from date, without a manual step
Lifecycle
Five stations, clearly separated
Each station is a separate library with its own permissions. Where a document sits determines who can see it and what may happen to it.
- 1
Editing
Editors work on the Word file with check-out, minor versions and comments. Feedback rounds collect expert input before approval starts.
Visible to
editors and contributors - 2
Review and approval
Tasks for reviewers and approvers, in the order and with the rules of your organisation. If required, the document is locked against changes during approval.
Visible to
workflow participants - 3
Distribution
Approved but not yet in force: the upcoming version is readable and acknowledgements are running. The current version applies until the effective date.
Visible to
readers - 4
Valid
On the valid-from date, the version becomes the valid one. Readers have read access only; the next revision continues separately in editing.
Visible to
everyone with access - 5
Archive
Expired or withdrawn documents move to the archive. It remains traceable what applied when.
Visible to
as defined in your concept
If you do not need lead time, skip the distribution station: approved documents then apply immediately.
Building blocks
What Smarter DMS includes
Every building block is in daily use at customers. You decide which ones your rulebook needs.
Approval with your roles
One to three stages, sequential or parallel, with a four-eyes rule, an upstream gate or joint approval by two managers. Deadlines, reminders and delegation are included.
Documented acknowledgement
Each person on the distribution list receives a task for the specific version. Reminders and escalation run automatically, and managers can pass the task on to their teams. The record is kept per person and version.
PDF with cover sheet
On approval, the Word file becomes a PDF with cover sheet, header and footer: title, version, scope, validity and approval date. Excel, Visio and CAD files stay in their original format.
Traceable changes
An approval record keeps reviewer, approver, date and comment for each version. A change comparison shows old and new side by side, and the version history can be exported as a PDF.
Valid-until and periodic review
Before expiry, the system reminds document owners. Depending on your rules, the document is extended, revised or archived, automatically or with its own approval.
Find instead of search
The process map is the entry point, with full-text search and filters by document type, process and scope. Personal views show open tasks and the documents that concern a person.
In SharePoint and Teams
One workspace for readers, editors and administrators, as a SharePoint page or as an app in Microsoft Teams. Notifications are sent by email from templates you maintain yourself.
Acknowledgement that counts as evidence
An opened document is not evidence. Smarter DMS creates a task for each person on the distribution list, tied to exactly one version. Confirmation is an active step, recorded with date and user account.
- Distribution lists from organisational units, groups or regions
- Deadlines before the effective date, reminders and escalation to those responsible
- Managers pass acknowledgements on to their teams
- Reports on open and completed acknowledgements, including export
- External recipients receive the PDF by email and their reply is documented
More than 500,000 documented acknowledgements for a single customer.
From Word to the valid version as a PDF
Editors write in Word. Readers receive a PDF that cannot be changed by accident and shows on every page which version they are looking at.
- Cover sheet with title, version, purpose, scope, valid from and valid until
- Footer with version, approval date and page number
- Logo per organisational unit or company
- Preview before approval, so the result can be checked in advance
- Can be switched off per document if the original format should be kept
Note for printed copies
If required, the first page states that printed or downloaded copies are not subject to change control.
Core and customisation
The lifecycle is the same. The way through it is different for everyone.
No two approval workflows are alike, as the five examples below show. That is why we do not deliver an off-the-shelf product, but a proven core that we configure for your rulebook with you and extend where your process requires it.
What the core provides
- Separate libraries for editing, distribution, valid documents and archive
- Workflows and tasks in SharePoint lists, without Power Automate
- Date logic for valid from and valid until
- Acknowledgement, reminders and mail templates
- Workspace with search, tasks and process map
What we define with you
- Roles, approval stages and deputies
- Document types, numbering scheme and required fields
- Scopes and distribution lists from your organisation
- Deadlines, reminders and escalation paths
- Cover sheet and layout of the PDF output
- Special rules, for example for safety-relevant documents
Five examples from practice
All five run on the same lifecycle. The differences are in roles, rules and deadlines.
- Infrastructure operator
- Quality coordination, reviewer, line manager. For certain areas, two managers have to approve jointly. Formal changes take a fast lane: version 4a becomes 4b.
- Maintenance
- A gate first decides whether the document goes into review. Then all reviewers have to approve, and the process owner releases it. The valid-from date must be at least 14 days in the future.
- Transport operator
- All approvers decide in parallel. For safety-relevant documents with short lead time, advance communication has to be confirmed. Acknowledgements are distributed by region and duty roster.
- Logistics group
- The document owner sets reviewers and deadlines. When the review deadline passes, the workflow moves on to the approvers, who all have to approve. Interface and emails come in three languages.
- Manufacturer
- Reviewers from the responsible department, then approvers. One decision per stage is enough. Approved documents apply immediately and validity ends after three years.
Built-in tools or app?
When are Microsoft’s built-in tools enough?
Not every document library needs a DMS. For a team with a few documents that apply immediately, the built-in SharePoint tools are the right choice.
The built-in tools are enough for this
- Documents that apply as soon as they are published: major and minor versions with content approval.
- Approval by one person: approvals in SharePoint libraries or Power Automate.
- Statutory retention periods: retention labels in Microsoft Purview.
This is what Smarter DMS is built for
- Two versions at once: valid and upcoming, with a switch-over on the effective date
- Multi-stage approval with roles from your organisation instead of hard-wired people
- Acknowledgement per person and version, with reminders and reporting
- PDF with cover sheet, footer and approval note from the metadata
- One entry point for everyone via process map, search and personal tasks
If the left column covers your case, you don’t need an app – you’ve already paid for the built-in tools. Smarter DMS exists for everything on the right.
Approach
From your process to a running solution
- 01
Capture the process
We walk through your document lifecycle: document types, roles, approval stages, deadlines, distribution. The result is a workflow that business and IT both support.
- 02
Set up and adapt the core
Libraries, metadata, workflows and mail templates are built in a test environment. Special rules and interfaces are developed on top.
- 03
Migrate existing documents
Existing documents move into the new system with metadata and version status, for example from SharePoint 2016. References between documents are checked along the way.
- 04
Pilot and rollout
One area starts with real documents. What comes up there is incorporated before everyone switches.
- 05
Operation and further development
Standards and organisations change. We support the solution and adapt it with you.
Technology
Built on Microsoft 365 and Azure
Smarter DMS uses the platform you already run. No second document system is added.
- SharePoint Online
- Documents, metadata, tasks and evidence are stored in libraries and lists in your tenant. There is no additional database.
- Workspace built with SPFx
- An application based on the SharePoint Framework, usable as a SharePoint page and in Microsoft Teams.
- Azure Functions
- Workflows, scheduled runs and PDF generation run as .NET services in Azure, deployed by pipeline and infrastructure as code.
- Microsoft Graph and Entra ID
- Emails and PDF conversion use Microsoft Graph. Permissions follow your groups in SharePoint and Microsoft 365.
- Integrations
- Organisational data from the HR system, handover to an existing archive system or other interfaces are built in the project.
Frequently asked questions about Smarter DMS
Is Smarter DMS a finished product?
Smarter DMS is a proven solution core, not an installation package from a store. We bring the lifecycle, data model and workspace. Roles, approval stages, deadlines and special rules are configured for your process in the project and extended where needed.
Which management systems is the solution suitable for?
For all that need controlled governing documents: quality, environmental, occupational health and safety and information security management, as well as an integrated management system that combines several standards in one rulebook. Documents can be assigned to several systems and filtered accordingly. Certification itself remains the responsibility of your organisation.
Is Smarter DMS audit-proof?
Smarter DMS makes it traceable who reviewed, approved and acknowledged which version and when, and separates editing from the valid version through permissions. Audit-proof storage in the legal sense additionally depends on retention, deletion protection and organisation. For this, the solution can be combined with retention policies in Microsoft Purview. For one customer, every published version is additionally handed over to the company’s archive system.
Do we have to use all building blocks?
No. One customer works without staging and publishes immediately, another without acknowledgement, and others generate PDFs with a cover sheet. The lifecycle stays the same; you choose the building blocks.
Do we need Power Automate or additional licences?
No. The workflows run as dedicated services in Azure and store their state in SharePoint lists. You need SharePoint Online and an Azure subscription for the services.
Can existing documents be migrated?
Yes. In previous projects we migrated content from SharePoint 2016, including metadata and version status. References between documents are checked and rewritten in the process.
What does Smarter DMS cost?
The effort depends on how close your workflow is to the existing core and which special rules, interfaces and migrations are added. After an initial conversation and a look at your process, you receive an assessment of effort and approach.
Further reading
Document control in detail
The posts in this series look at individual building blocks and at the differences between workflows.
SharePoint as a DMS: where major and minor versions end
SharePoint offers a lot for document management. For controlled documents with an effective date, multi-stage approval and acknowledgement, built-in tools end.
Read postValid from: distributing documents before the effective date
How an approved document in SharePoint is readable before it applies: staging library, switch-over on the effective date and the questions to settle first.
Read postSharePoint document approval workflow: five real-world examples
Five examples of approval workflows for controlled documents in SharePoint. Which questions shape the workflow and why a standard workflow rarely fits.
Read postRead confirmation in SharePoint: proving acknowledgement
SharePoint has no read confirmation for documents. What a record of acknowledgement must contain and how distribution lists, deadlines and reminders interact.
Read postISO 9001 document control with SharePoint
What ISO 9001 clause 7.5 requires for the control of documented information, what SharePoint covers and where controlled documents need more.
Read postBuilding an integrated management system in Microsoft 365
One rulebook for quality, environment, occupational safety and information security: how process map, metadata and roles carry an IMS in SharePoint.
Read postControlled digital work instructions: from Word to the valid PDF
How a Word file becomes a controlled work instruction: number, approval, PDF with cover sheet, a stable link at the workplace and periodic review.
Read postIs SharePoint audit-proof? What a DMS must prove
Audit-proof storage is not a switch in SharePoint. What the term requires, what version history and Purview do and what a DMS proves for controlled documents.
Read postHow does your document approval work today?
Show us your workflow. One work instruction and one approval are enough. You get an honest assessment of what the core covers and what we would need to adapt.