Notes / Team / 4 min read

Coverage when someone is out

WhizSuite · 2026-09-01

Write the cover before the out-of-office, when everyone is still calm enough to share passwords properly.

A named cover per brand

Each active brand needs a second person who can find the calendar, the locked files, and the approver rule. "Ask in the general channel" is not a cover.

The cover shadows one approval cycle before they are alone. Reading a doc is not the same as moving a row.

Access that is not a sticky note

Use seats and roles, not shared passwords in a chat. If a tool forces a shared login, store it in the agency's password manager and rotate it when staff leave.

Check the cover can actually open the scheduler and the inbox a week before the leave. Permissions rot.

Shrink the week if you must

If cover is thin, reduce what publishes. Tell the client. A quieter week is cleaner than a cover person inventing captions in a voice they do not know.

Pre-lock the posts that must go out. Leave the cover with monitoring, not with concepting.

A real out-of-office

The person on leave states the cover's name and stays out. Answering "just this one" trains the client to ignore the cover forever.

On return, read what shipped before you change the system. Assume something drifted. It usually did, a little.

Join the waitlist