Protecting the record when a ticket changes

Every approved version is saved automatically — editing a ticket later never touches what your GC actually signed.

The problem

When a ticket gets edited after your GC signs off — a corrected quantity, an added line — it’s easy to wonder whether the version they actually approved still exists, or if it’s been quietly overwritten.

How Sub's Flow solves it

  1. 1

    The ticket stays approved through edits

    Editing a ticket after approval doesn't undo the GC's signature. It only reverts to Pending Approval if you explicitly resend it for a fresh signature.

  2. 2

    Every approval gets its own snapshot

    The moment a ticket is signed, a permanent record capturing exactly what was approved at that moment is saved automatically — no extra step required.

  3. 3

    Later edits don't touch the record

    Change a quantity, add a line, whatever the correction — the original approved snapshot stays exactly as it was, untouched by anything that happens afterward.

  4. 4

    Include the history in your export — if you want it

    When you export or invoice a ticket, you can choose to include the prior approved snapshot alongside the current version — it's there as backup whenever you need it, not something forced into every export.

Built with these features

Ticket versioning

Approval status tracking

Questions about ticket versioning

Never lose what was actually approved