What a briefing actually contains

A briefing from Toolcabinbase is a document your people lead can print or send as a short file before a manager sitting. It is written in the language you chose at kickoff. It quotes the employee experience app’s own counts, not a parallel score we invented.

Opening page

The first page is deliberately dull: which app, which dates, which sites, who sat in the working sessions, and what was out of scope. If contractors were missing from the roster, that sentence appears here so nobody treats a later gap as a mood.

The ninety-day map

The map is a single sheet. It marks pulse send dates, reminder bursts, shutdowns, festive weeks, and any late language pack. A dip that sits on a shutdown is labelled as such. We would rather the map look busy than leave a manager to guess.

Quiet and heavy

This section names groups in your language — packing hall, night shift, KL office, Johor plant — and says whether they still open the app, whether they answer the first items only, or whether they have stopped. We do not rank them as winners. We say what the trail shows.

Comments, with a fence

We do not reprint every remark. You choose the sample or the export rules. We describe where comments pile up and where they vanish, and we keep individual wording out of the packet unless you have already shared that wording in a supervised session and asked for it to be paraphrased.

The conversation list

The last working page is short. It lists manager conversations the numbers can bear, and a second list of sentences we would not take into a huddle. That second list is often the part people remember.

If you want this packet, the route is a flagship review or a quarterly cycle once the cuts exist. A workshop produces marked notes, not this full briefing. Write to us with the app and the window.