# Why your procedures age badly. A **quality procedure** isn't a text you write once and for all. It's an object that moves — or should move. And the way it ages says a lot about the health of your documentation system. Too much, or not at all Documents revised dozens of times (up to 52), others still in force but 15 years old. Too much movement, or none at all. Rarely the right cadence. Observed on a real production document set (anonymized figures). The cause is simple: **the heavier a format is to produce, the more expensive it is to maintain.** A 40-page PDF — you think twice before reopening it. So either you patch it endlessly, or you let it fossilize. Either way, the know-how drifts away from practice — and the procedure goes stale. The problem isn't the content — it's the format and the structure. When knowledge is locked inside monolithic documents, every update is expensive: re-reading, re-distribution, re-training of everyone qualified. So you put it off. And a procedure you keep putting off updating is a procedure that goes stale. Two levers break this vicious circle — two complementary answers developed at Sinfony. ## Structure the foundation, streamline training. ### Structure the foundation — Maestro A procedure ages badly first because it's poorly broken down: it mixes the stable principle with the step that changes often, so a small update forces you to reopen everything. Maestro rationalizes your document base — detecting duplicates and contradictions, breaking it into reusable grains, building a clear architecture (RACI, flowcharts, logical levels). Once the foundation is structured, an update touches only the grain concerned, not the whole corpus. [maestro.sinfony.ai ↗](https://maestro.sinfony.ai/en) ### Keep know-how alive — Hoctav Restructuring isn't enough if training stays prohibitively expensive. Hoctav is our AI video studio: it turns a procedure or a piece of know-how into a short training video in minutes, with no camera and no editing. Updates then take minutes, not weeks; you only redo the module concerned; and a learner retains a step they've seen and practiced far better than a paragraph they've read. Keeping know-how current becomes viable again — so it actually gets done. [hoctav.ai ↗](https://hoctav.ai/en/) ## Documenting and training are no longer two worlds. The classic trap: the procedure lives in the DMS, training lives elsewhere, and the two drift apart on their own. By linking the **document grain** and the **video module**, a change propagates at once to the format _and_ to the training. The procedure stops rotting because it stops being expensive to keep true. ## Go further. [ ### The document lifecycle Over-revision, fossilization: a single cause. Read →](/en/blog/quality-document-management-lifecycle/)[ ### Simplify 800 documents −50% documentation volume. Read →](/en/blog/simplify-800-documents-documentation-volume/)[ ### Make your DMS talk A data X-ray of the document repository. Read →](/en/blog/data-analysis-dms-document-repository/) ## Procedures that age, in plain terms. Why does a quality procedure age badly? + Rarely from a lack of rigor: it's because maintaining it costs too much. A heavy format (a PDF dozens of pages long) discourages you from reopening it, so you patch it endlessly or let it fossilize. Either way, the document drifts away from practice and goes stale. Should you revise your procedures more often? + The right cadence is neither "more" nor "less": it settles on its own once maintaining becomes cheap. It's by lowering the cost of updating — by structuring the foundation and streamlining training — that you get a healthy revision cadence. How do you update your procedures without blowing up costs? + By breaking knowledge into grains (the stable principle separated from the variable step), so you only revise what changes — and by producing the associated training as a short video, redone in minutes. Documenting and training then stop being two separate worlds that each drift on their own. ## Your procedures don't rot from a lack of rigor. They age because maintaining them costs too much. Lower that cost, and the right cadence settles in.