It arrives on a Friday, usually between 18:30 and 19:00. “Can you just post this real quick?” The attachment is a screenshot of a document. There is no link. The logo is forty pixels wide. The only direction is “make it pop”. On approval, the note says the boss is fine with it, probably.
Every social media manager has a version of this story. Here is a slightly less stressful way to handle the next one.
Why “real quick” is never quick
A single post touches several small decisions: the right version for each network, a working link, an image with alt text, and someone with authority saying yes. Each of those takes a minute when planned and twenty when rushed. The person asking sees one post; you see five tasks and a risk.
Agree the rules on a calm day
- A cutoff time. For example, requests after 16:00 on Friday are published on Monday unless they are urgent.
- A definition of urgent. A real incident or a time-bound announcement, not “the CEO likes it”.
- Who approves. A named person, not “probably fine”.
- What you need. Text, link, image, approver. Missing pieces mean it waits.
Let the process say no for you
When a rule exists, “first thing Monday” is not a personal refusal, it is just how things work. A shared calendar helps too: the requester can see that Monday at 9:30 is a perfectly good slot, and the approval stage shows who still needs to say yes.
And when it really is urgent
Sometimes it is. Then do the minimum safely: one network, one version, a second pair of eyes, and a note to review it on Monday.
GPTpost has approval stages and a shared calendar for exactly these conversations: oraglegpt.org.


Leave a Reply