Skip to content

Your team ships only the revision someone approved.

For you, an editor and whoever signs off, Oat gives each person a role and releases one approved revision.

The current way costs hours you do not have.

  • Nobody can say which shared-doc version was approved.
  • Monday's sign-off covers a piece that changed Tuesday.
  • When something goes wrong, nobody can show who changed what.

Oat turns those hours into one read.

  1. Step 1

    Give each person a role

    Four roles, and one person can hold several.

  2. Step 2

    Request changes or approve

    Send it back with comments, or approve the hash.

  3. Step 3

    Check the trail

    Every revision, comment and approval carries who and when.

Roles decide who can do what.

One approval is required to leave the Desk, and assignment never grants authority over a piece.

Roles

  • Owner manages access and voice rules.
  • Editor edits and submits for review.
  • Approver signs off one exact revision.

Every handoff is on the record.

Every assignment, submission and change request is recorded on the piece, so a handoff never loses a decision.

Handoffs

  • Assign a piece and the editor is notified.
  • Request changes with comments on passages.

Every save is a revision and one ships.

Each save is an immutable revision, and an edit after approval sends the piece back to review.

The trail shows who approved which words.

Every approval, comment, role change and delivery carries who did it and when.

Bring your archive and arrive to work already waiting.

Request access

Invited access. Bring your editor and whoever signs off.