postroom.

Client caption approval status report: show what needs a decision

Copy a caption approval status report that separates approved versions, revisions and blocked inputs. Includes a fictional batch and a publishing handoff check.

Report the next decision, not just the number of drafts

A useful client caption approval status report answers three questions: which saved captions have a decision, which ones need the client to act, and what the publishing operator can safely take next. A single percentage hides those differences.

Use one reporting cutoff and count the current versions in the agreed batch. If a caption was approved yesterday and edited today, report the revised version as needing a new decision. Yesterday’s approval does not make today’s wording ready.

I built PostRoom around decisions on specific caption versions. The report below is a worksheet you maintain alongside the room; I do not provide an automatic client status report or a connection to your publishing queue.

Separate decisions from dependencies

Choose a small set of plain-language states and explain them once. A draft awaiting an offer date is blocked by an input. A complete caption sent for review is waiting for a decision. Those need different people and different messages.

Do not combine all unfinished work into “pending client.” That can blame the client for writing still owned by the freelancer. It also makes the next action hard to identify.

For publishing, add a separate readiness field. Caption approval says something about text; it does not prove the asset, crop, destination preview or scheduled time is ready.

  • Writing: the creator has not submitted a complete saved version.
  • Blocked input: name the missing fact and the person supplying it.
  • Awaiting caption decision: identify the submitted version and final approver.
  • Changes requested: the creator owns a revision before another review.
  • Caption approved: the decision belongs to the named current version.
  • Publishing hold: a separate unresolved dependency prevents scheduling.

Copy a short batch status report

Send the report through the client’s existing agreed channel. Keep private review links and caption text out of public updates. A report can refer to stable caption IDs so the client can find the full wording in the review room.

The count at the top and the detailed rows should describe the same batch at the same cutoff. Name an owner for every next action; “we are waiting” is less useful than “Alex confirms the offer date.”

Worksheet or example — select and copy

CAPTION APPROVAL STATUS

Client / batch:
Status as of: [date, time, timezone]
Batch scope: [caption IDs]
Current versions approved: [count] of [count]
Awaiting client decisions: [count]
Changes requested: [count]
Blocked inputs / still writing: [count]

ID | Current version | Caption state | Next action | Owner | Agreed cutoff
[POST-01] | [v2] | [Awaiting decision] | [Approve or request changes] | [Approver] | [Date/time/zone]
[POST-02] | [v1] | [Blocked input] | [Confirm offer end date] | [Fact owner] | [Date/time/zone]

Caption-ready handoff: [IDs and versions]
Separate publishing holds: [ID / unresolved asset or preview check / owner]
Decision requested now: [specific action]
Next update: [agreed time or meaningful change]

Fictional example: three captions, two different blockers

This example is fictional. At Tuesday’s reporting cutoff, a workshop client has three captions. POST-01 v2 needs a fresh decision after its location changed. POST-02 v1 is approved, but the designer has not delivered the final image. POST-03 v1 is still being written because the client has not confirmed capacity.

The correct headline is one current caption version approved out of three. It is not “the batch is one-third ready to publish”: even the approved caption has a separate asset hold.

The useful request to the final approver is “Please decide on POST-01 v2.” The request to the fact owner is “Please confirm the capacity for POST-03.” The designer gets the asset request separately. This keeps the status report from becoming an unstructured group chase.

Worksheet or example — select and copy

FICTIONAL TUESDAY UPDATE

POST-01 v2: awaiting caption decision; Maya to review the changed location.
POST-02 v1: caption approved; publishing held until Leo supplies the final image.
POST-03 v1: writing blocked; Maya to confirm workshop capacity.

Caption decisions: 1 approved / 1 awaiting review / 1 not submitted.
Publishing handoff today: none.
Next action: Maya decides on POST-01 v2 and confirms capacity; Leo delivers the image.

Reconcile the report before exporting

Open each claimed approved item and compare its current saved version with the report. Remove superseded versions from the ready list. If your counts do not reconcile, fix the rows before sending the headline.

In PostRoom, I keep CSV export limited to approved captions. Treat an export as a snapshot: text already copied elsewhere does not update when a draft changes. The publishing operator still checks the destination copy and its separate holds.

You can rehearse an approval, an edit and a fresh decision with fictional content in the demo. Then try the report on one small client batch and ask whether the client could identify their next action without a second explanation.

If the report is passing to a publishing owner, attach the ready-text references and unresolved holds to a receiving checklist so a status count is not mistaken for a complete handover.

Sources and product references

Continue with a related guide