Skip to content
Crystal Desk
Revision Tracking

Every version. Stored. Visible. Comparable.

Rejected work never overwrites the original — every iteration is timestamped, attributed, and visible downstream.

Unlimited iterationsPer-field controlVisible downstream

When a script is rejected and sent back for rework, the writer submits a new version — and Crystal Desk stores both as separate, timestamped iterations. The reviewer sees v1, v2, v3 side by side, not just the latest overwrite.

This isn't limited to scripts. Any field on any stage's completion form can be marked "revision enabled" by the workflow admin — an audio file, a block of copy, a duration value, a reference link. Every change is captured with a timestamp and the submitter's identity.

Revision history isn't locked to the reviewer, either. It's visible at every downstream stage — so the voice artist can see exactly what the script went through before it reached them.

v1Initial draft — 30 second Hindi radio spot for Diwali sale...3 days ago
v2Revised per brand team feedback, tightened opening line...2 days ago
v3Final approved version2 days ago
- Grab your Diwali deals today.
+ Grab your Diwali deals today — only at your nearest store.
What You Get

Everything included, out of the box.

Per-field revision control

Any field — text, audio, duration, a reference link — can be marked revision-enabled by the workflow admin.

Unlimited iterations

Store as many rounds of rework as a ticket actually needs, with no cap.

Timestamp & submitter on every version

Know exactly when each iteration was submitted and by whom, human or AI.

Visible at every downstream stage

A voice artist can see the script's full revision trail even though they weren't part of the review.

Rejection reason captured

Every rework loop stores why the previous version was sent back, not just that it was.

Latest value by default

The current version shows first everywhere; full history is one click away, not the default view.

How It Works

From setup to production, step by step.

1

Work is submitted

The assignee completes a revision-enabled field as part of their stage's completion form.

2

It's reviewed

A reviewer approves it, or rejects it with a reason — sending it back for rework rather than silently overwriting it.

3

The new version stacks, not replaces

The resubmission becomes a new, separate iteration — v1 stays intact, visible side by side with v2.

Questions

Frequently asked

See it work on your workflow.

Start free, build your first workflow in minutes, and see the difference structure makes.

✓ 14-day free trial   ✓ No credit card required   ✓ Cancel anytime