Finish a content batch · Practical guide

Turn scattered photos and ideas into a content batch you can actually review

Turn a small set of photos and ideas into three posts someone can approve.

About 4 minutes · Original FTS guide · 22 Oct 2026

A review-ready content batch groups selected photos, caption notes, permissions, and approval status.

A camera roll full of good material can still leave you with nothing ready to post. To finish a batch, you need a small selection, a clear purpose and a review decision for each piece.

Start with three posts. This is a manageable first batch, not a posting-frequency recommendation. You can repeat the process after you know where it gets stuck.

You need access to your source photos or clips, the current facts about your business, and a document where a reviewer can see the proposed posts together.

1. Give the batch one job

Write one sentence about the audience and what the batch should help them understand.

For a fictional local repair business: “Help nearby homeowners understand what we repair and how to ask about a job.”

Then give each post a different role:

  • Answer one question.
  • Show one piece of work or process.
  • Explain one next step.

This keeps you from making three versions of the same announcement.

2. Select a small set of usable assets

Choose a few candidates for each post. Record where the original lives, who created it and whether you have permission to use it for this purpose.

Check for customer names, screens, addresses, paperwork or other private details in the frame. A photo you possess is not automatically cleared for public marketing. Put uncertain material aside until the right person confirms permission.

Keep originals unchanged. Work from copies when cropping, editing or adding text.

If you do not have a suitable image, the answer may be a clear text-led post. Avoid inventing a customer result or using a stock image in a way that implies it shows your actual work.

3. Build a review card for each post

Each card needs:

  • Working title.
  • Audience question or purpose.
  • Selected image or clip.
  • Proposed caption.
  • Intended next step.
  • Facts and permissions still to check.
  • Reviewer and status.

Here is a fictional example:

Working title: What to send with a repair inquiry Purpose: Help someone make a useful first inquiry. Visual: An approved photo of a repairable item, without customer details. Caption: “A clear photo and a short description can make the first conversation easier. Tell us what the item is, what has stopped working, and where you need help. Please leave private paperwork out of the photo.” Next step: The business's verified inquiry page. Check: Confirm that these are the details the business actually wants.

The example is a writing pattern, not a claim about FTS's services or another business's process.

4. Write for the person looking at the post

Start with the useful point. Add only the detail needed to understand it, then give one clear next step.

Check names, dates, prices, opening hours and links against a current source. Remove claims you cannot substantiate. Keep private customer information out of the caption, even when the photo is cleared.

Read the text aloud. Replace expressions that sound impressive but explain little. If the reader has to guess what you want them to do, make the next step more specific.

5. Include the information beyond the visual

Where the publishing platform supports alternative text, describe the information the image contributes. A functional image may need its action described; a purely decorative image has a different purpose. W3C's image decision tree helps distinguish these cases. Put essential details such as an event date in readable text too.

For video with meaningful audio, prepare and review captions. Automatic captions can be a starting point, but check names, wording, timing and important sounds. W3C's caption guidance explains what captions need to communicate.

These steps are part of a useful review. They do not replace a platform-specific accessibility check.

6. Ask for decisions, not general reactions

Send the three review cards together. For each one, ask the reviewer to choose:

  • Approved as shown.
  • Changes needed, with the exact change.
  • Hold, with the missing fact or decision.

Keep feedback beside the relevant post. If two people disagree, identify who owns the final decision rather than trying to merge incompatible instructions.

After making a change, show the updated version. Do not assume that approval of an earlier draft covers a materially different image, claim or offer.

7. Separate approval from publishing

A review-ready batch is finished when the reviewer has everything needed to decide. It is approved when the authorized person approves the actual versions. Publishing is a separate step.

Before scheduling or posting, confirm the account, final files, captions, destinations and timing. Do not promise a posting schedule or result just because the batch exists.

Your next move

Use the Content Batch section of the Finish This Project checklist to prepare three review cards. You should finish with a visible status for every post, not another folder of possibilities.

Want help choosing your next step? Open Finish Finder, or explore Finish the Stuff with your review cards ready.

Optional next step

Keep the batch—or bring us the production work.

The guide is complete on its own. If the review cards are clear but producing the connected campaign is still stuck, bring us the material you already have.

Discuss the workUse the free Finish FinderKeep reading in Campus