Your team ships only the revision someone approved.

Everyone gets a role. Only the exact version an approver approved goes out.

Why freelance women in Delhi and Bengaluru are still chasing 60-day-old invoicesRevision 2 of 2, edited by Harsh Songra yesterday

Changes requested

AngleHarsh Songra, on paragraph 1

Good idea, boring hook. Open with the invoice that is 60 days late, not with the category. The number is the story.

Approval binds to c4e2b71. A later edit returns the piece to review.

How it goes with Oat.

Step 1
Give each person a role
Invite by email or WhatsApp number.
Step 2
Ask for changes or approve
Feedback goes on the passage it is about.
Step 3
See who approved what
Every revision shows its feedback and its approver.

Pinned to the paragraph, so the next revision answers it.

Passage feedbackInvoices piece, paragraph 9, revision 2 of 2

Before

Remember, you are worth every rupee on that invoice. Believe in yourself and chase it with confidence.

VoiceYou, on paragraph 9

cut the pep talk about confidence. never do that.

After, this draft only

The invoice is 60 days late. The next message names the date, the amount and the day the late fee starts.

Revision 3 of 3, changed by Oat from your comment.

Proposed voice rule, every later draftAwaiting your decision

Do not lecture the reader about confidence or self-care.

Accepted rules live in Context, versioned, and any of them can be undone.

Roles decide who can do what.
Owner, Editor, Approver and Viewer. Oat never approves anything itself.
Change it and it comes back.
An edit after approval sends the piece back to review.