Which version should your team use?
I build applications that help teams link documents to a job, record feedback on the right version and see which version has been approved.
Document workflows
From draft to approved version.
When different versions sit in inboxes or folders, teams often need to ask which one to use. A defined review process keeps the job, the draft and the approval decision together.
- Link documents to a job or case
- Distinguish versions and define access
- Record feedback and approvals by version
Concept example
An addition is awaiting approval.
A project team adds on-site training to the scope of work for a client job. The project lead comments on the new version. The team can see which version it should continue working from.
- V1Approved for use
- V2Under review
Work included
Installation and functional testing.
Added On-site training.
Project lead · Feedback on V2
Please specify how many people the training is for.
Version 1 remains in use. The current version stays in place until a new version is approved.
Initial scope
Start with one document type.
We choose one document type, such as a scope of work. We then define which job it belongs to and who can review and approve each version. More roles or review steps can be added later.
Plan for storage and access.
An existing file store can be connected where a suitable interface is available. We discuss access and retention early. Special archiving or electronic signature requirements are considered separately.
Your next step
How does your team identify the approved version?
Describe which documents your team regularly reviews, where they are stored and who approves them. Together we can see how to simplify the review and make the approved version clear.
Jonas Noah SchulzOwner · Software developmentAlready have a specific idea?
Outline your scope and, where possible, get an indicative cost range.

