# Your procedures circulate, get approved and reach people.

What happens between the moment a procedure is written and the moment the right version reaches the right person.

## The problem

A written procedure is worth nothing until it is approved, distributed and read by the people it concerns. **That is where everything gets lost.**

Approval is chased by email and stalls. Nobody knows which version is authoritative. Superseded documents keep circulating in shared folders. And on inspection day, who approved what, and when, has to be reconstructed by hand.

The tracking spreadsheet always ends up lying — not through carelessness, but because it is not the system where things actually happen.

## The walkthrough

The walkthrough 2 min 06 — click to play. The video only downloads at that point.

[Download the video (MP4)](/assets/videos/module-5.mp4)

**Maestro is under development.** This video comes from the MVP — the product running today, not the final platform. As of today, Maestro is used only within Sinfony consulting engagements.

## What the module does

Eight functions, as they appear to the people who use them.

1

### Every document has an identity and a version

A number, a version, a fingerprint. You always know which version is authoritative, and which one superseded which.

2

### An approval route that cannot be bypassed

Review first, approval second, in order. Approval requires all designated approvers, with a signature.

3

### People only see what they should see

Visibility depends on the document's status and the viewer's role: the version in force, the one coming, or the history.

4

### Comments anchored in the text

Like in a word processor: a comment sits on a specific passage, carries a status and gets closed. No more feedback scattered across emails.

5

### States change on the right dates

A procedure becomes effective on the planned day and expires on its own. Nobody has to remember, so nobody forgets.

6

### Who did what, and when

Every action is attributed to a person and written to an audit trail that cannot be rewritten. It is the first thing an inspector asks for.

7

### Notifications go out by themselves

Nine triggers: to review, to approve, expiring soon, new version released… Follow-up stops being a chasing job.

8

### A document to read becomes training

Mandatory reading of a procedure is tracked like any other training item, and signed off the same way.

## Two kinds of company, two uses of the same module.

Regulated large enterprises

### Cover the grey zone upstream of your official document system.

You already have a regulated document system and you are not going to replace it. This module keeps the documents Maestro produces alive until they enter that system.

-   The upstream phase stops being a black hole of spreadsheets and emails
-   An audit trail over the zone your inspectors always end up looking at
-   No migration: your official system stays exactly where it is

Expert SMEs & mid-market

### The document control you need, without the platform.

You have no document system, and a full regulated platform costs more than the problem it solves. This module gives you what is useful, without the weight or the price.

-   Versions, approval, distribution, expiry, traceability
-   Nothing to administer: no six-month rollout project
-   Inspection-proof without a large-group budget

[Document management software: what to look for →](/en/document-management-software/)

## The nine Maestro modules

Each module is sold and used on its own. See how this one fits with the other eight.