Revisions

Keep derived document work visible

flowchart LR
    Source[Source document] --> Revision[Revision]
    Revision --> Approval[Approval]

Revisions are for document work that should stay visibly connected to a source record while still having its own path forward.

In the product

The revisions tab lists each derived package with its revision type, version range, and source template.

Creating a revision starts by choosing the template plus the source and target versions that define the comparison range.

Teams can compare the selected versions before generating the revision package so the branch stays reviewable from the start.

Separate the source from the derived work

That distinction matters because teams often need to evolve a document without blurring the current source record and the new in-progress path.

Use revisions when the branch matters

Use a revision when:

• the team needs a derived path from an existing document
• reviewers need to understand how the new work relates to the source
• sign-off may come later, but the first problem is keeping source and derived work distinct

On the workflow

The revision model keeps three things visible:

• the source document
• the derived revision work
• the possible handoff into approval once sign-off matters

Keep the distinction crisp

Revisions are not the same as approvals. A revision governs derived work on the content itself. Approval governs formal review state around the resulting content.