Email Digests
Nobody opens a dashboard they don't already have a reason to open. Digests are GarmentFlow's answer: four emails, sent on a schedule, each one telling one leader what changed in their area and what needs a decision.
They are the only part of GarmentFlow that comes to you rather than waiting for you.
The four digests
| Digest | Goes to | Covers |
|---|---|---|
| Production | Production Manager | Where the work is, what is running late, bottlenecks, output by unit, quality flags on the floor |
| Design | Sample Manager | Sample pipeline, samples needing you, open pattern requests, measurement deviations, patterns changed |
| Logistics | Stock Manager | Shortfalls needing ordering, ordered-not-arrived, material requests aging, consumption pending, ready to dispatch |
| Quality | Quality Manager | Top defects, trending up, units spiking, on hold now, open non-conformances, per-unit quality |
Recipients are resolved by role, not by a mailing list. Everyone holding the role gets the email; nobody has to be added or removed by hand when a person changes job.
When they arrive
All at 07:00, server time:
- Daily — every morning.
- Weekly — Monday.
- Monthly — the 1st.
Daily and weekly are the working rhythm. Monthly widens out — most of the monthly digests carry a last four months trend section, which is the view you can't get by looking at today.
Quiet days stay quiet
A daily digest suppresses itself when there is nothing to act on. No overdue batches, no shortfalls, no defect spikes — no email.
This matters more than it sounds. A digest that arrives every single day regardless of content gets filtered into a folder within a fortnight, and then it stops working. One that only arrives when something needs attention keeps its meaning.
Weekly and monthly always send: their job is the trend, and "nothing happened" is itself a result worth seeing.
What's in one
Each digest has the same shape:
- A KPI strip across the top — the four or five numbers that define the area.
- Sections, each a short table with a heading and a time window. Rows are colour-toned: green where healthy, amber where it needs watching, red where it is already a problem.
- Buttons into the relevant Desk screens — the production digest links straight to the Production board, the schedule and Where Is It.
An empty section says so — Nothing overdue on the floor — rather than disappearing. Knowing a check ran and found nothing is different from the check not running.
Where the numbers come from
The production digest reads the same endpoint the Production workspace uses, so the WIP-per-unit number in your inbox is the number on the board. The rest come from the operation ledger directly, and from the existing reports for the richer tables.
There is no separate digest database and no nightly snapshot to fall out of date. If a digest disagrees with a dashboard, they were built at different moments — not from different data.
Previewing one
You don't have to wait until 07:00 to see what a digest looks like. A Manufacturing Manager or System Manager can build any digest on demand and have it emailed to themselves — including in another language, which is the practical way to check a translation before it lands in someone's inbox.
Ask your administrator to run the preview, or see API & Integrations.
Turning them off
Digests are role-driven, so the way to stop receiving one is to not hold the role — which is usually the right answer, because the role is what says the area is yours.
If a whole digest should stop for the site, that is a scheduler change; talk to your administrator.
Digests are translated. Someone whose desk language is Spanish gets a Spanish digest, in the same email, on the same schedule.
What to do next
Digests point at screens. Start with Dashboards for the production ones and Quality dashboards for quality. For alerts about a specific quality event rather than a daily summary, see Alert Configuration.