The schedule

The schedule is not a list of posts. It is where time gets attached to work.

A cut goes out on Thursday at six. A reminder to film B roll lands on Monday. A job re-cuts last week's material every Friday morning. Posts are one of the things on it, not the only thing.

It belongs to the team#

A team shares one calendar. A schedule that is private to each person is a rota nobody can plan around.

Google Calendar connections are the exception. Those are per person, because the access is.

What can sit on it#

• Posts. A finished cut going out to a platform at a set time.
• Reminders. Something a person needs to do.
• Repeating jobs. Work that runs on a cycle.

Repeating rules are ours rather than a rented service, so they behave the same everywhere and do not stop working because someone else's product had an outage.

If it ran, there is a record#

Every run writes a record before it starts and another when it finishes. "Did that go out?" is answered from data, not from guesswork.

That includes the times the answer is "it tried and it failed", which is exactly when guessing is worst. The schedule tells you a post failed instead of showing it as scheduled forever.