Chapter 1 · The resource
Get an important update read and know who read it
Follow this course in your space: your progress is saved, and the community answers your questions.
Follow for free"But I posted it in the group chat." That line always comes too late: the new process wasn't followed, the supplier's price change wasn't accounted for, the client got the old version. Writing something down isn't enough. It has to be read, by the right people, on time, and you need to be able to check.
Why important updates get ignored
Before the fixes, the causes. An important update slips through the cracks when:
- it's buried in a chat between two jokes and a lunch photo;
- it's too long, and the key point is hiding in the fifth paragraph;
- it's addressed to "everyone," so each person assumes it's mostly for the others;
- it has no deadline, so it waits behind everything that does;
- everything is marked "important," so nothing really is.
Four moves to get it read
1. Say what to remember in one sentence
Before the document, the note or the link, write the one sentence to remember. If the person reads only that, they've got the essentials.
- Vague: "Here's the new delivery process."
- Clear: "Starting July 1, every delivery is photographed and the photo is added to the task before it leaves."
2. Choose exactly who it's for
Not "the team," but the people concerned, by name. An update for the two installers doesn't need to go to the bookkeeper. Fewer recipients means a better chance each one feels it's for them.
3. Set a "read by" date
"Read by Friday at noon" turns information into action. Without a date, it waits.
4. Check who read it, and follow up only with them
This is what's missing most often. A "seen" in a chat app doesn't mean the person read the attached document. You need an explicit confirmation: each person marks it "Read."
Several tools can do this. In Flopilot, for example, the "To read" feature is built for exactly this: you send a document, a note, a link or a message, pick one or more people or the whole project, can flag it as important and set a "read by" date; each person checks "Read" and you see who did and when. Without a dedicated tool, a simple "Reply 'read' when you're done" and a list of names to check off will do.
On the deadline, follow up only with the people who haven't confirmed, privately. Everyone else doesn't need a reminder they have no use for.
The template to copy
READ BY [day, date, time] [IMPORTANT, only if it truly is]
For: [names]
Key point: [the one sentence to remember]
What this changes for you: [one or two concrete lines]
Full document: [link]
Please confirm "Read" once you've read it.
Example for a wedding photographer working with two second shooters: "Read by Thursday at 6 p.m., for Ines and Tom. Key point: for Saturday's wedding, no photos during the ceremony, at the couple's request. What this changes: you stay at the back of the venue until the recessional. Full timeline: [link]."
Save "important" for what is
Keep the "important" flag for updates that, if unread, would cause a mistake, lose money or create a problem with a client. If you use it more than once or twice a week, it stops working.
The full checklist for this resource
Copy it and go through it with your team.
CHANNELS
- [ ] Each channel has a single purpose, written in a shared guide
- [ ] Expected response times are written for each channel
- [ ] Anything about a task lives in the task itself
- [ ] Anything that needs to last lives in a note or document
- [ ] After a call, the decision is written in the right place
MESSAGES
- [ ] The request is on the first line
- [ ] The context fits in two lines
- [ ] Every request has a date
- [ ] The link goes straight to the right document
- [ ] One question per message
- [ ] The four templates (request, heads-up, decision, follow-up) are pinned
MEETINGS
- [ ] 15-minute format, always in the same order
- [ ] Agenda filled in by everyone the day before
- [ ] No round of progress updates
- [ ] Meeting canceled if nothing's blocked and no decision is pending
MEETING NOTES
- [ ] Written during the meeting, by someone who isn't running it
- [ ] Three sections: decisions, tasks with who and when, open questions
- [ ] Sent within the hour, always in the same place
- [ ] Tasks are created right after
IMPORTANT UPDATES
- [ ] The key sentence comes first
- [ ] Recipients are chosen by name
- [ ] A "read by" date is set
- [ ] Each person confirms "Read"
- [ ] Only those who haven't read it get a follow-up
- [ ] "Important" is saved for what truly is
Your turn
Pick one important update your team needs to know this week. Send it with the "Read by" template: key sentence, named recipients, deadline, request for confirmation. On the deadline, note who confirmed and follow up only with the others. Then go through the full checklist with your team and choose together the two points to put in place first.
Recommended tool
All your projects in one place
Flopilot brings your tasks, documents, notes and conversations together by project, solo or as a team.
Premium
Unlock every course of the group Flopilot
Every lesson, new courses as soon as they come out, and the community. No commitment.