The dangerous row in a social calendar is not the one you forgot to fill. It is the one marked “scheduled” while the client still has not approved the final caption, or the row attached to the wrong account. If you manage several clients alone, your spreadsheet needs to answer three questions before you open a publishing tool: which account, which local time, and which exact version is cleared to go live?
This guide adapts the planning method in TASKUL’s Japanese social-post spreadsheet article for Australian client work. It keeps the useful idea of making empty publishing slots before writing content, then adds explicit approval and time-zone checks. The example below is fictional, and your agreement with each client controls who can approve a post.
Start with a slot, not a finished caption
Set up one row for one post to one account. A campaign that runs on Instagram and X is two rows, even if the idea is shared, because the caption, asset, account and live URL can differ. Do not use one row for an entire client or a week’s worth of posts; you will lose the ability to tell which version actually went live.
At the end of a month, place next month’s agreed slots in the calendar. Fill the client, exact account handle, platform, local date and time, time zone, and Slot state. Leave the idea and asset fields empty until you know what the post will say. An empty slot is a visible piece of work, not a failure of planning. Australia’s business.gov.au social-media guidance also recommends planning content in advance with a calendar; the frequency and format still need to fit the audience and the client’s resources.
Do not add a month’s worth of speculative commitments just to make the sheet look full. Use the post count and cadence in the client agreement. If a client wants an extra post, record the decision and revise the plan rather than silently growing the workload.
Keep the columns that prevent real errors
The Japanese source uses 11 columns for a solo operator. It correctly gives account and platform their own fields. For Australian client work across several states, a single publish timestamp without a named time zone is too ambiguous. A client-facing approval process also needs an approver and a record of which version was approved. The working CSV therefore has 17 fields, but you fill them at different moments rather than completing a long form before every draft.
| When you fill it | Fields | The decision they support |
|---|---|---|
| When making a slot | Client, platform, exact account handle, local date, local time, time zone, format, state | Is this the right destination and the intended local publishing moment? |
| During production | Idea or hook, caption version ID, caption text, asset version link | What exactly is being reviewed and copied into the scheduler? |
| Before scheduling | Approval owner, approval record, claims and rights check | Is this version authorised and safe to publish? |
| After publishing | Published URL, learning note | Did the planned post go live, and what should change next time? |
The approval record can be a dated email or a link to a client review system. It should identify the approved caption and asset version, not just say “approved” in a cell. A Done or Approved status that refers to an older version does not clear a later edit. The example keeps the complete short caption in its own cell so you can compare it with the scheduler, while the version ID ties that text to approval. Keep sensitive client material in the client’s own approved storage; the downloadable example uses invented brands and contains no real client information.
The claims and rights check field is a prompt to inspect a promotional statement, image permission or other issue relevant to the post; it is not a legal sign-off. The ACCC’s social-media promotions guidance says businesses must be able to substantiate claims in social posts. If a price, result, product benefit or testimonial has changed, check it against an approved source before publishing.
Work through two Australian clients in one week
Suppose Ava is a fictional freelance designer and social manager. She drafted the following week’s posts on the previous Thursday and sent both versions for review. Now it is Tuesday 10 November 2026: the Sydney studio’s post for Wednesday 11 November is approved, while the Brisbane café’s post is still awaiting a decision on a product claim. Each client has a different account, asset folder and approver. Neither is a TASKUL customer or a performance case study.
| Client and destination | Intended local publish time | State on Tuesday | Next action |
|---|---|---|---|
Sydney studio · @example_sydney_studio · Instagram |
Wed 11 Nov, 09:00 Sydney time (AEDT) | Approved version 3 | Confirm the scheduler shows this account, caption and asset before scheduling |
Brisbane café · @example_brisbane_cafe · Instagram |
Wed 11 Nov, 09:00 Brisbane time (AEST) | In client review | Hold the slot; ask the approver to verify the revised product claim |
These are two separate 9 a.m. local slots, not the same instant. Sydney observes daylight saving in November; Brisbane does not. The Fair Work Ombudsman’s daylight-saving guidance lists NSW among the places that change clocks and Queensland among those that do not. The NSW Government’s time-zone definitions identify AEDT as UTC+11 and AEST as UTC+10. In this example, Sydney’s 09:00 is 08:00 in Brisbane. Verify the city and date in the actual scheduler rather than copying a time label from last season.
The Sydney row can move from Approved to Scheduled only after Ava opens the scheduler, reads the selected account handle against the row, checks the scheduled date and time zone, and previews the exact caption and asset. The Brisbane row stays in In client review. A missed response does not turn it into approval. Ava sends a short update: “The revised caption is ready for your review. I am holding Wednesday’s slot until you approve this version. If it is not approved in time, I will propose the next available slot.” This message is an operational example, not a statement about what every contract requires. If the agreement explicitly defines another approval mechanism, use it and retain the decision source.
The Sydney caption in the example CSV is version 3: “Small rooms need clear walkways. Which corner would you redesign first?” The approval record names caption v3 and asset v3. The Brisbane draft says, “Our seasonal iced drink uses local strawberries.” That sourcing claim is deliberately unverified in this fictional example; Ava must get a substantiated, approved version or remove the claim before any scheduling. The example never treats a pending draft as a published advertisement.
The calendar should expose the missing decision instead of hiding it behind a date.
A state should tell you what can happen next
Avoid Nearly done and Waiting maybe: they do not identify the next action. Use a small set of states tied to observable events. Slot means a date exists but the content is not drafted. Draft means a version is being made. In client review means the named approver has the version. Changes requested means the version needs work. Approved means the approval record names the version that will publish. Scheduled means the scheduler has been checked against that version. Published means you verified the live post and saved its URL. Held means the slot has been deliberately paused with a reason and next contact date.
| From | Move only when | Otherwise |
|---|---|---|
| In client review → Approved | The authorised person approves the exact caption and asset version | Keep it in review, or move the slot to Held and ask for a new date |
| Approved → Scheduled | The scheduler’s account, local time and uploaded version all match the row | Correct the mismatch before saving the schedule |
| Scheduled → Published | The post is visible on the intended account and its URL is recorded | Investigate a failed or delayed scheduled post; do not mark it live automatically |
This state model is intentionally stricter than the Japanese source article’s suggestion that no reply by a deadline can sometimes be treated as approval. For a client post, do not infer consent from silence unless the actual agreement clearly authorises that process. Even then, check that the scheduled version and scope fit that agreement. The calendar itself cannot grant publishing authority.
Set the spreadsheet’s location before using dates
In Google Sheets, open File → Settings and inspect both the locale and the time zone. Google’s help page says these settings apply to the entire spreadsheet and affect date and number formatting. A shared file can therefore display or interpret values in a way a colleague did not expect. Use a clear YYYY-MM-DD date field and a separate HH:MM local time field in the CSV; keep the IANA-style place name, such as Australia/Sydney or Australia/Brisbane, in the time-zone column. The name remains useful when daylight saving changes the offset.
The Japanese formula =TEXT(C2,"aaa") is specific to a Japanese display convention. For an English weekday in Google Sheets, Google’s TEXT function documentation specifies ddd for a short weekday name. If your local date is in column D and Sheets has recognised D2 as a date value, a helper column can use =TEXT(D2,"ddd"). If the imported value is plain text, convert that column to dates first and check a sample row. The downloadable CSV leaves formulas out so it opens cleanly in Excel and other spreadsheet software; add the helper only if the weekday catches a real scheduling mistake for your workflow.
A spreadsheet’s time-zone setting does not magically convert every pasted local time into the right client city. Read the time shown by the publishing platform before saving. If you work across states or daylight-saving transitions, use a time-zone converter for that specific date and record the city in the row. A note saying only “AEST” can become wrong for Sydney after the clock change.
Make the weekly routine serve approval time
The Japanese article groups similar work by day, which is useful for a solo operator. An example week is Monday for reviewing last week’s live posts and filling open slots, Tuesday for choosing angles for next week, Wednesday for gathering assets, Thursday for drafting and sending next week’s versions for client review, and Friday for scheduling next week’s already approved posts. Anything still in review remains unscheduled and gets its own follow-up. Move the days to match your clients’ review windows. If approvals typically take two working days, a Thursday draft cannot safely depend on a Friday morning reply for a Friday post. In Ava’s example, last Thursday’s Sydney draft stayed in review until Tuesday 10 November and can be scheduled only after that approval; the Brisbane draft remains outside the scheduler.
After publication, save the live URL and one useful observation. For example: “The answer to the opening question drew relevant replies; keep the question, shorten the second paragraph.” Do not copy a dashboard of metrics into every row. If reporting needs detailed numbers, use a separate report with a defined measurement window, because platform metrics can change after the first day.
The worked calendar CSV shows Ava’s two clients, an approved Sydney post, a Brisbane post awaiting approval and the next actions. The blank CSV is free without registration. Import it into a private sheet and replace the invented handles and links before using it with client work. If clients need access, give each client a separate file or a deliberately restricted view; do not expose another client’s captions or assets in a shared master sheet.
To make the sheet usable, create a private Google Sheet, import the CSV, and check that each field landed in its own column. Set the locale and time zone in File → Settings, confirm column D is recognised as a date and column E as a time, then freeze the header row. Add a filter so you can inspect one client or one account at a time. For the State column, use a dropdown containing only the eight states defined above; it prevents approved? and nearly done from becoming accidental permission to schedule. Finally, sort by local date within each time zone, not by an assumed nationwide clock. If a client will review the file, make a separate client-only copy rather than sharing your multi-client master.
Before each scheduling batch, filter for the target account and check whether a matching post already has a Scheduled or Published row on that date. Repeated themes can be intentional, so a duplicate-looking idea is a prompt to inspect the live URL, not an automatic error. The final account check still belongs inside the publishing tool.
Do the last check in the publishing tool
The spreadsheet organises decisions; it does not schedule or publish posts. TASKUL is a project and task-management product with an English product page. Do not assume that TASKUL can post to Instagram, X or another network, or that it can approve content for a client. Use the calendar and your chosen publishing tool for those steps.
Before clicking Schedule, compare five things side by side: the exact client account handle, the platform, the local date and time zone, the caption and asset version, and the approval record for that version. For a promotional post, also inspect claims and permissions. After it goes live, open the link from the intended account and copy its URL back into the row. If a scheduled post fails, the state returns to Held with a next action; it does not become Published because the planned time passed.
If several client projects are competing for production time, the multiple-project guide helps distinguish ready work from work blocked by a client’s answer. If the client’s feedback is ambiguous, use the feedback decision guide before changing a version that was already approved.
Questions about using this calendar
Should I keep every client in one spreadsheet?
Keep one private master if it helps you see your workload, but share only a client-specific file or restricted view. Separate files are safer when clients will directly edit or review rows, or when one mistaken filter could expose another client’s campaign. The number of accounts alone does not decide this.
Should an unanswered approval request become a scheduled post?
No, unless an actual written agreement defines that authority and the exact version falls within it. Otherwise keep the post in review or hold the slot, tell the client what decision you need, and propose a new time. A spreadsheet deadline is not an approval.
Is the same 9 a.m. time usable across Australia?
No. Record the city or time zone for each account and check the date in the scheduling tool. Sydney and Brisbane can differ by one hour during Sydney’s daylight-saving period. The audience’s useful posting time is also something to test, not a universal rule.
Do I need a new row for a revised caption?
Keep the same row if it is the same planned post, but change the linked version and move the state back to review if the revision needs approval. Create a new row when a second post will go to a different account, platform or slot. This keeps the live URL attached to the exact published post.
