**Module under development.** This page describes what the module will do. The other modules are available today.

# Design forms that are easy to fill in.

Batch records, logs, tracking sheets: what people fill in every day, and what generates most documentation deviations.

## The problem

The form is the most completed document in the company, and the worst designed. **That is where deviations are born.**

An ambiguous box, a missing unit, a field filled in out of habit without looking: every design flaw is paid for in entry errors, then in investigations.

Far too much is asked for, too. Whole columns are collected because they always have been, without anyone using them — and every data point collected is one more chance to get it wrong.

## The two-minute walkthrough

The two-minute walkthrough The module is not mature enough to be filmed yet.

**Maestro is under development.** This module is not mature enough to be filmed yet — the video will come. As of today, Maestro is used only within Sinfony consulting engagements.

## What the module will do

Five planned functions, described as they will appear to the user.

1

### Every data point has to earn its place

A column stays if someone uses it, or if a requirement demands it. Otherwise it goes. That is what lightens the load fastest.

2

### Criticality sets the rigour

Not all data is equal: what commits product quality is handled differently from what merely supports monitoring.

3

### The form follows the task

Field order follows the order of operations, not the org chart of the department that designed it.

4

### Entry that leaves no room for doubt

Units, expected ranges, formats: what is expected is stated in the field, not in a footnote.

5

### Paper, glass or application

The same specification produces a simplified paper form, a paper-on-glass screen or an in-app entry, depending on the workstation.

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

Regulated large enterprises

### Reduce what you collect, not just what you write.

Your batch records are the bulk of the documentation produced every day, and the primary source of deviations. That is the richest seam.

-   The volume of data collected cut back
-   Fewer entry errors, therefore fewer investigations
-   Batch record review time reduced accordingly

Expert SMEs & mid-market

### Leave the home-grown spreadsheet without running a project.

Your records live in Excel files that everyone adapts. The module gives them a clear, stable shape, with no platform to deploy.

-   Records a new joiner can read
-   No more spreadsheet versions drifting apart
-   A clean base the day a customer audits you

[Replacing Excel for procedures and records →](/en/replace-excel-for-procedures/)

## The nine Maestro modules

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