Social Desk · Date planning

Plan Social Post Dates Without Confusing Calendar Order With a Schedule

Use Social Desk’s date-only calendar, same-day order and CSV export carefully, with clear time-zone notes for the person publishing your posts.

A social plan can have the right captions and still leave a practical question unanswered: which post should go out first? A date alone does not settle that question, especially when several platforms, reviewers or publishing time zones are involved.

Shane’s Social Desk provides fields for a date, platform, campaign, caption and notes. Its Content calendar arranges cards by the dates you enter. Use that view to organize the work, then keep the precise publishing instructions alongside it. This guide focuses on date handling and post order, so a tidy calendar does not hide an unfinished timing decision.

1. Treat Post date as a day, not an appointment

The current Post date control accepts a calendar date. There is no dedicated publishing-time or time-zone field, and the tool does not convert a date into a scheduled social-platform action. It saves the entered date and displays it on the card.

Choose what that day means for your campaign. For example, it could be the intended publishing date in the audience’s local market. State that convention before entering a batch of posts. If a team works across markets, a date without its intended time zone can produce different interpretations.

Use Notes for short, explicit instructions such as “Target: 09:00, America/New_York; publisher to confirm in the destination platform.” The time-zone name is a written instruction for a person. Social Desk does not read that note as a scheduling rule or perform a conversion.

If a post is tied to an event, distinguish the event’s start time from the post’s intended publishing time. “Workshop at 14:00” is not enough to tell a publisher when to release the announcement. Verify the time and any daylight-saving change in the publishing service you actually use.

2. Resolve undated cards before reviewing the week

Post date is optional. A saved post without one displays Date not set, and undated cards appear before dated cards in the current ascending sort. A card at the top of the list may therefore be an unfinished idea rather than the next item due.

Start each planning review with those undated entries. Decide whether each needs a real date, more information or a place outside the active plan. Do not assign an arbitrary date just to move a card down the screen; that can make an unresolved idea look ready to publish.

The current cards have no general edit control. To change a saved date or note, export a reference copy, save a corrected replacement, and remove the obsolete record after checking the replacement.

The calendar is a collection of cards, not a week-limited scheduling grid. It includes stored past and future dates, and the interface has no date-range or week selector. A Published post can still appear near the top because its old date sorts before newer work. Read both the date and status when deciding what needs attention.

3. Put the same-day sequence in the instructions

Dated cards appear in ascending date order. When two saved posts have the same date, the current view retains their saved order; it does not sort them by a time written in Notes. Card position is therefore a poor way to communicate which same-day post comes first.

Consider this fictional launch plan. You enter the recap first while collecting ideas, then add the announcement:

• Recap: November 12, 2026; Instagram; Notes: “Sequence 2; target 16:00, America/New_York; publish after the announcement is confirmed.”
• Announcement: November 12, 2026; LinkedIn; Notes: “Sequence 1; target 09:00, America/New_York; confirm the launch page is live first.”

With All platforms selected, the recap remains before the announcement because both dates match and it was saved first. The notes make the intended sequence clear despite that display order. The times are illustrative, not a recommendation for the best time to post.

Review dependencies as well as clock times. A launch announcement may need a working product page; a recap may need approved photos. If a prerequisite fails, pause the actual publishing step rather than treating the recorded date as permission to proceed.

4. Check the full plan before narrowing the view

The calendar’s filter selects a platform. It does not filter by campaign, status or date. A campaign name helps you recognize related cards, but entering that name does not create a separate campaign calendar.

Review All platforms first to catch overlapping messages and dependencies. Then switch to an individual platform to check that its planned posts make sense together. Return to All platforms before deciding the whole campaign is ready, because a platform filter can hide the related post that must happen first.

Keep campaign names consistent and put the sequence or timing instruction in each relevant record. Do not rely on one explanatory card that disappears when someone narrows the view.

5. Recheck order in the exported file

Export posts CSV downloads social-calendar.csv. Its date column preserves the entered date, and Notes preserves your written timing instructions. The export includes all saved posts in saved order, not the current platform filter or the calendar’s date-sorted order.

For example, if you save a November 13 post before a November 12 post, the calendar shows November 12 first while the CSV retains November 13 first. Sorting the cards has not rearranged the stored records.

Before handing the file to a publisher, make a working copy and sort or filter it deliberately in a spreadsheet. Check the intended date range, campaign and platforms, then review the notes for time zones and sequence. If the publishing service needs separate time or time-zone columns, prepare those in that service’s required format and inspect its preview. Social Desk’s CSV should not be assumed to be a compatible bulk-scheduling file.

A short timing check before publishing

1. Resolve Date not set entries and distinguish old posts from current work.
2. Confirm the intended day, local time and time zone for each time-sensitive post.
3. Write the same-day sequence and any prerequisites in Notes.
4. Review the full campaign across platforms, then check the exported rows and their order.
5. Schedule or publish through the destination platform or your publishing service, and verify the result there.

Social Desk keeps the plan in this browser. It does not publish, schedule to social platforms or send reminders. A clear date convention and a few precise notes give the person doing that final step a much more useful plan.