Stop chasing your team for updates. The report still lands Monday at 8.

Every Friday your agent asks each person, privately, what they got done. Monday morning you get one report in your team's own words, plus the executive version for your manager or leadership updates. Nothing goes out until you've read it.

What it does

Ask every contributor privately on the Friday, in their own 1:1 chat or by email.
Group the week into the streams the work actually falls into, read from what people wrote.
Compile the report in a fixed order, in each person's own words, and deliver it on the agreed morning.
Draft the executive version from that same material and hold it for your approval.
Publish the week you approved to the dashboard, and confirm the link.

What you get

One report a week, same shape every time, in your team's own words.: Grouped by workstream, with the attention items written out in the message rather than buried in the document.
An executive version framed around decisions, risks and what changed.: Written from the team report the same morning, and held in the chat until you sign it off.
A dashboard link that keeps working, with every approved week on it.: The newest approved week opens first. A picker at the top goes back through the history.

What it needs

Who submits an update, and an email for each
Who the report is for, and who it goes to next
Which morning it should land, and at what hour
What happens when someone has not submitted
Whether there is a shorter executive version

The ask goes out on the Friday. The report lands Monday at 8, or whichever morning you pick.

Nothing reaches anyone senior until you have read it. The board changes only when you approve a week.

Who runs it

One room, and it is the one the install already ran in. The report, the executive draft, the approval and the board link all land there. Contributors are the deliberate exception: they are asked one to one, so nobody's thin week is read by the rest of the team.

Asked privately, reported in their own words: Each person is asked in their own 1:1 chat, or by email if they are not on Bolter yet. Their section reaches the report as they wrote it, not paraphrased.
Anyone who should read it joins this chat: Adding a reader means adding them here, not opening a second room. Contributors stay out of it on purpose, because that is what keeps the ask honest.
One link to forward, not a screenshot: The board holds every approved week at a URL that keeps working, so a reader can go back to June without anyone reconstructing it.

What stays yours

The approval gate is the point: The executive version is posted for your read and goes no further until you say so. If there is no reply by the afternoon it chases you once. It never publishes unapproved, however late the week gets.
Workstreams come out of the work: You never define them and never maintain them. They are read from what people actually reported, kept stable so weeks stay comparable, and re-derived when the work moves. The week a grouping changes, the report says so.
The record is separate from the report: Every submission is kept as it arrived, with its time and the channel it came in on. That is what answers what somebody actually delivered months later, without anyone arguing about it.
Addresses stay off the board: Contributor emails are held in the agent's own store because the Friday ask needs them. The board is a link people forward, so nothing on it carries an address.

Questions

Do the people on my team need Bolter accounts?: No. The Friday ask goes to the email address on record and they can reply to it. The same email invites them in. Anyone who joins gets a 1:1 chat and is asked there from the next Friday. Anyone who does not stays on email and the report works the same.
What is everyone actually asked?: Three things, and only these three. What they completed this week, what they plan for next week, and what needs your attention. Anything needing a decision, a budget, an introduction or an unblock goes under the third heading.
What happens when someone does not submit?: You pick the rule at install: ship on time with the missing sections labelled plainly, or hold and chase. Either way a late or thin submission is reported as what it was. Delivered late is delivered, never a miss.
Can I skip the executive version?: Yes. Answer no at install and the second responsibility, the approval gate and the dashboard all drop out. You are left with the team report going onward as it is.
Where does everything get posted?: In the one chat the install ran in, renamed to the reporting chat. The weekly report, the executive draft, the approval and the board link all arrive there. No second room gets opened.
Can it read our meeting notes too?: Optionally. Any meeting-notes tool with an API and folders you can scope a read to. It folds in what was decided in meetings, attributed to the meeting rather than to someone who never wrote it down, and flags a conflict rather than overruling a person's own submission.
Who can change what is on the board?: Only an approval. The board takes nothing from outside and its only writer is the agent, so a week appears there because you approved it. Publishing exposes it to your workspace, and reaching further is a visibility change a person has to make.
Can I move the day and the hour?: Yes, at install. Pick the morning the report is actually used, ideally an hour before the meeting it feeds. The Friday ask moves with it, always the last working day before the weekend ahead of delivery.

Stop chasing your team for updates.

Install it, name who submits and who it is for, and the first asks go out on the Friday.

Browse all Bolter blueprints