Your weekly workstation report: how hard your Mac actually ran
It is easy to lose track of how hard you lean on a machine. A few overnight runs here, a marathon build day there, and by Friday you have no real sense of how much your Mac actually did. The weekly Mac workstation report is a quiet look back: it adds up the last seven days from the local Activity Log so you can see the week your machine had, not the one you remember.
What the report adds up
The report aggregates the last seven days of the local Activity Log into a few plain numbers: total runtime hours, your single longest session, and counts of the events that happened along the way.
Those numbers answer questions you cannot eyeball. Did that one overnight job really run for nine hours, or did a safety limit stop it sooner? How many separate keep-awake sessions did the week actually contain? The log already records each decision; the report just rolls a week of them into a summary.
It is a feedback loop more than a dashboard. The point is to notice patterns, like a Mac that quietly racked up far more awake time than you thought, or a week with more thermal events than usual.
The Workstation Score, honestly
The Workstation Score is a single 0 to 100 number, and the math behind it is deliberately simple. It starts at 100, subtracts 8 for each thermal warning, and subtracts 6 for each emergency sleep, then clamps the result between 0 and 100 and attaches a rating, good or needs attention.
Read that as a stress signal, not a verdict. A lower score means the week included more moments where the Mac was warned about heat or had to sleep under pressure; it does not mean anything is broken, and a high score is not a clean bill of health.
It is a heuristic. The score is there to draw your eye to a rough week, not to diagnose hardware. If it keeps dipping, treat that as a prompt to look at where and how you are running long jobs, not as a measurement of damage.
Related guideThe safety governor: why LidRun won't keep a hot or idle Mac awakeIt stays on your Mac
Everything in the report is computed locally from the Activity Log already on your machine. Nothing about your runtime, sessions, or score is uploaded anywhere.
That matters because this data is, frankly, a portrait of how you work: when you run long jobs, how hard, how often. It is yours, and the report keeps it that way.
LidRun's separate, opt-out telemetry is a different thing entirely and far narrower, just a random install id and coarse details like app version for update checks, with no serial, no machine name, and no email. The weekly report is not part of that; it never leaves the Mac.
Using it as a feedback loop
The most useful habit is to actually glance at it. A week where the score dipped and thermal events ticked up is a nudge to check the obvious things: where the Mac sits, whether it had airflow, whether long runs were on a hard surface instead of a couch or a closed bag.
If you see a lot of emergency sleeps, that is the safety governor doing its job, letting the Mac sleep rather than pushing the hardware past your limits. Frequent ones are a sign your runs are bumping into thresholds often, which is worth understanding even though each one was the safe outcome.
Use it the way you would use a step counter: a rough, honest signal that nudges better habits over time. It will not cool your Mac for you, and it does not promise your hardware is fine, but it does make a hot or stressed week impossible to miss.
LidRun keeps your work running with the lid closed, with battery and thermal safety built in.
Frequently asked
It aggregates the last seven days of your local Activity Log into total runtime hours, your single longest session, and counts of the events that occurred, plus the Workstation Score.
It starts at 100, subtracts 8 for each thermal warning and 6 for each emergency sleep, then clamps the result to a 0 to 100 range and gives it a rating of good or needs attention.
No. The report and score are computed locally from the Activity Log on your Mac and nothing is uploaded. LidRun's optional, opt-out update telemetry is separate and never includes this data.
No. The score is a heuristic stress signal, not a diagnosis. A low score means the week had more thermal warnings or emergency sleeps; treat it as a prompt to check placement and airflow, not as a measurement of harm.