All stories
Logistics
Example story
How an operations team turned weekly reporting into a ten-minute review
An operations team stopped writing its weekly report by hand and now reviews a one-page draft from Runlance in about ten minutes.
Mid-size logistics company
−85%
reporting time
3
connected sources
100%
briefs reviewed
The challenge
Every Friday, two team leads in the operations group spent most of the afternoon on the same job. They collected updates from three places: project pages in the docs tool, threads in team chat and ticket changes in the issue tracker. Then they merged everything into one weekly report for the Head of Operations and the regional managers.
The work was repetitive, but it was not simple. Updates were spread across dozens of pages and channels. Some were out of date, some contradicted each other and some only existed as a short reply in a chat thread. The team leads had to check each one before it went into the report.
The result was a report that arrived late, often on Monday instead of Friday. It ran to several pages, and most readers skimmed the first section and stopped. Blocked work was sometimes buried halfway down, so decisions waited another week.
The Head of Operations wanted three things: the report on time, short enough to read in one sitting and clear about what needed a decision. The team leads wanted their Friday afternoons back. Both sides agreed on one condition: nothing would go out without a person checking it first.
The solution
The team started with a single workflow in Runlance. It runs every Friday at 8:00 and follows the same chain each week.
Gather updates from the docs tool, team chat and the issue tracker, limited to the projects and channels the team chose.
Group the updates by project and flag anything blocked or overdue.
Draft a one-page brief with headline changes, blockers and decisions needed, each with its source cited.
Wait for one of the two team leads to review.
The reviewing team lead reads the draft, opens a source when a detail looks off and either approves it or requests changes with a short note. In the first weeks, most notes were about grouping and wording. When a project page was out of date, the team lead fixed the page and replayed the run instead of editing the draft by hand.
After about a month, the review settled at around ten minutes. The brief now goes out before lunch on Friday. Every brief has been reviewed by a person before sharing, and the regional managers say they read it to the end because it fits on one screen.
The team leads now spend the time they saved on the blockers the brief surfaces, rather than on finding them.
We stopped writing the report and started reading it.
Head of Operations
Another story
One more team that hands a weekly task to Runlance and keeps a person in charge of every result.
All customer stories
