Notes / Calendars / 4 min read

Put the shoot on the same week

WhizSuite · 2026-10-16

Production dates belong on the content calendar. A separate shoot doc becomes a rumor.

One timeline

If the photos must exist before the posts, the shoot is a predecessor of those rows. Put it on the same week view the account manager already opens. A calendar nobody checks will not save you.

Include who is on set, what must be captured, and which posts are blocked until the files land. "Brand shoot" with no outputs is a party.

Backups before the day

Assume the shoot moves. Have two rows that can publish from assets you already hold. If every post in the week depends on Tuesday's photos, Tuesday owns your retainer.

Tell the client that dependency out loud. They often move shoots without telling the person who promised a Friday post.

Selects are a status

Raw files are not a finished tile. Add a status for selects and retouching so the calendar does not jump from "shoot" to "scheduled." That jump is where ugly crops come from.

The person who picks selects should know which formats are coming: vertical, square, thumbnail. A gallery of horizontals will not save a Story week.

After the files arrive

Drop the chosen frames onto the rows they unblock and retire the shoot item. Leaving it forever makes the month look busier than the feed.

If a planned shot failed, mark the dependent posts as blocked the same day. Waiting until the publish morning is how the team finds out together.

Join the waitlist