Versions

A study keeps changing after the report has gone out: someone adds a machine, the client sends a revised drawing, a shift pattern is corrected. Six weeks later a question comes back about the figures in the document they signed, and the live study no longer shows them. A version is the study as it was at one moment — fleet, assumptions, plan, results, aisle check — kept whole.

#When one is saved

On delivery

Marking a study delivered saves a version automatically. That is the one the client has.

By hand

On the report page, Versions → say why → Save a version. Before a board pack, after a site visit, whenever a number is about to be quoted.

Each version records who saved it, when, why, and carries a copy of the plan file as it was, so a drawing that has since been replaced can still be downloaded.

#Reading one

Open a version and you get the report as it stood, printable, with a footer saying which version and when. Compare with live lists only what has changed since: a fleet line that went from 6 × 3 to 8 × 3, a demand figure, a verdict that flipped from short to meets, a scale or plan file that changed. Nothing changed, it says so.

#What a version is not

It is not a branch. You cannot edit a version or restore the live study from it; a version is evidence, not a draft. To try a different fleet on the same plan, use a scenario. Versions are exported with the organisation and are available through the API as /studies/{ref}/versions; they are deleted with the study.