# Write a procedure once, and write it well.

A procedure is not written in front of a blank page: it is assembled from what the analysis and the RACI have already established.

## The problem

Writing a procedure takes three weeks. **Reviewing it takes six.** And the result is a document nobody will open.

Every author has their own style, plan and level of detail. Two procedures from the same department look nothing alike, and the operator has to relearn how to read each time.

The costliest part stays invisible: the same document mixes what must be understood, what must be decided and what must be done. Three audiences, three needs, one text — that nobody reads in full.

## The walkthrough

The walkthrough 4 min 49 — click to play. The video only downloads at that point.

[Download the video (MP4)](/assets/videos/module-3.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

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

1

### The procedure assembles from what exists

Purpose, scope, flowchart, RACI, watch-outs: the structure is filled with grains already classified, not retyped.

2

### What explains, what decides, what does

Each piece of content goes where it is useful: explanation into training, rules into the procedure, actions into the work instruction.

3

### The split is chosen, not endured

One parent procedure and several instructions, split by role, by equipment or by variant — the choice is explicit.

4

### Variants stop duplicating the document

Two lines, two sites, two products: what differs is isolated, the rest stays shared. No more copies that drift apart.

5

### The RACI lives inside the document

The responsibility table and the flowchart are part of the procedure, not an appendix nobody updates.

6

### A clean output, straight away

The document comes out formatted and ready to circulate — no layout pass before approval.

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

Regulated large enterprises

### The same structure across the whole group.

Twenty authors, twenty styles. The module enforces the structure and leaves the writing to the experts, where they add value.

-   An identical template across every site
-   The split decided explicitly, not endured
-   Local variants without duplicating the corpus

Expert SMEs & mid-market

### Write a procedure without being a technical writer.

You have no documentation department. The module supplies structure and level of detail; your expert only has to say how the work is done.

-   No need to know what a SOP is to produce one
-   The essentials written once, reused everywhere
-   A document the person doing the job can actually read

[How to write a procedure people actually read →](/en/how-to-write-a-procedure/)

## The nine Maestro modules

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