PhemosReach / Content workflow guides

Weekly social content plan template for a team of two (free download)

By PhemosReach, a Modus Future product · Published 16 October 2026

Most content calendars fail because they are too big. A month of empty boxes looks like a plan and behaves like a debt: the boxes get filled in a hurry, nobody reviews what went into them, and by the third week the calendar is quietly abandoned.

This template is one page a week. Five slots, one line per post, and the columns that make a post safe to publish: who it is for, what it says, where the facts came from, who writes it and who checks it. It is written for a team of two, and it works for one person doing both jobs across two sessions.

What is on the page

Each slot is one row. The columns, and why each one is there:

• Day. When it goes out. Pick the day on Monday; pick the time when the post is approved.
• Account. The exact account, not the network. "LinkedIn, company page" rather than "LinkedIn". The wrong account is the most common avoidable mistake, and it starts here.
• Reader. One person the post is for, in a few words: "a customer deciding whether to renew", "someone who has just found us". A post for everyone is a post for no one.
• The point, in one sentence. If it does not fit in a sentence, the post is not ready to draft. Write the sentence before anyone writes the post.
• Format. Text, image and caption, carousel, short video. Decide it now so the draft owner does not have to.
• Source, and the date it was checked. Every fact, price and date in the post needs a source. The date tells the reviewer whether to check it again.
• Draft owner. Who writes the first version.
• Reviewer. Who checks the message, then the finished post. Not the draft owner.
• Status. One of: idea, drafted, message reviewed, scheduled, published, failed. The status column is the plan's memory; it is what Monday's look back reads.
• Publish date, time and timezone. Filled in at scheduling, after the review. The timezone is written down because every team eventually publishes something at the right time in the wrong zone.
• Published URL. The link to the live post, recorded after it goes out. A scheduled entry is a plan; the URL is the outcome.

That is eleven columns. It looks like a lot for a social post. It is the minimum that lets the person who did not write the post check it properly, and it takes less than a minute to fill once the idea is chosen.

The Monday half hour

Fill the page in one sitting at the start of the week. Half an hour is enough once you have done it twice.

1. Look back (5 minutes). Read last week's page. Which rows reached "published"? Which stayed at "idea" or "drafted"? Was anything "failed"? Copy the published URLs somewhere you keep them, and move any unfinished idea either into this week or onto the later list.
2. Choose the ideas (10 minutes). Three to five, from three places: questions readers or customers asked you last week, work you can show, and something you can explain better than the sources your readers are finding. Reader questions first; they are the posts people are already waiting for.
3. Fill the rows (10 minutes). For each idea: the reader, the one-sentence point, the account, the format and the source. If you cannot write the point in a sentence or cannot name the source, that idea goes to the later list, not into the week.
4. Assign and book the reviews (5 minutes). Name the draft owner and the reviewer for each row, then put the two review sessions in the diary. A review that is not in the diary does not happen.

The rest of the week

• Tuesday: drafts written. Status moves to "drafted". The draft owner writes with the source open and the voice brief beside it.
• Wednesday: message review. The reviewer checks the facts against the source, the claims, the voice and the first line. Status moves to "message reviewed". Anything that fails goes back to the draft owner with a note, not a rewrite.
• Thursday: finished-post review and scheduling. The reviewer looks at the post as it will appear: the media, the caption as cut off by the platform, the account, the link, the date and the timezone. Then it is scheduled and the status says so.
• Friday: delivery check. Open each published post, confirm it is live and the link works, record the URL. Note any reader question that came in; it is a candidate for next Monday.

The checks in the two reviews are written out, item by item, in the social media approval checklist. Keep it beside the plan.

An example week

This is an illustrative example for a fictional two-person bookkeeping firm, not customer data and not a claim about which days or formats perform best.

Three posts, two accounts, two people swapping roles. The Friday row is behind: it will be reviewed Thursday afternoon or move to next week, and the Monday look back will say which.

Roles for two people, or one

With two people, swap the roles row by row so that each of you writes some posts and reviews the others. The reviewer should be the person who can say whether the claims are true; for anything technical that is usually the person who did the work, which is a reason for them not to write that post.

With one person, the roles are two sessions. Draft on Tuesday, review on Wednesday with the draft closed overnight. The gap does most of what a second person would. Write your own name in both columns anyway, with the session day beside it, so the plan still records that both checks happened.

Start with three slots

The template has five rows because a good week sometimes has five posts. Start by using three. The two spare rows are for the week a reader question arrives that is worth answering straight away, not for filling because they are there.

Add a regular fourth slot when the three have gone out cleanly, reviewed and on time, for a month. If a row stays at "idea" two weeks running, that is the plan telling you three is still the right number.

Download the template

• Download the plan as a text file, one page with five slots and the status values listed. Print one a week or keep them in a folder.
• Download the plan as a spreadsheet (CSV), with the eleven columns as headings and a row for each day. Add a sheet per week, or a row per post, whichever you will keep up.

Both files have the same columns as this page.

Keeping it going

Once a month, lay the four pages side by side. Count the rows that reached "published" and the rows that never left "idea". Look at which accounts got the most rows and whether that matches where your readers are. Then change one thing: the number of slots, the review day, or the kind of idea you choose first. One change a month is enough to find out whether it helped.

If the plan is being skipped, make it smaller before you make it stricter. A three-row page that gets filled every Monday is worth more than an eleven-column system that was used twice.

Using the plan in PhemosReach

The plan's rows map onto PhemosReach's review queue. A draft is held for review in two stages, the script first and then the image, and only an approved post goes out (scheduling is available from the Starter plan), so the "message reviewed" and "scheduled" statuses on the page correspond to steps the product records for you.

From the Starter plan, scheduling has cadence rules per account and a next best time suggestion, which take over the "publish date and time" column once a post is approved. The "account" column still matters: choose the destination deliberately and check it in the finished-post review, because the tool will publish to whichever account you picked.

For the full routine behind this page, including measuring whether the posts did anything, read social content planning for small teams. For the reviews themselves, use the approval workflow guide.

Put the workflow into practice

See how PhemosReach works, then compare plans and limits.