You worked all day. Which project received most of that time?
OGAD (Off Grid AI Desktop) can estimate the distribution from your captured Mac activity. With Pro capture enabled, Reflect groups observations into work areas and shows approximate time in Mind share. Use it to review patterns and plan your next week without manually starting a timer for every task.
Use the estimate to ask a better planning question
You might discover that one project appears throughout the day while another received only a short session. That can prompt a useful question: does next week's plan need more protected time for the second project?
The result is an estimate from sampled observations. It is not a stopwatch, a measurement of attention or a billing ledger. A window being visible does not prove that you spent every intervening second working on its subject.
Prepare the activity record
Use OGAD Pro on Mac with the required local analysis models. Review Screen Recording and Accessibility permissions, then choose Resume capture in Replay or the Capture settings section. Check the visible Capturing status. Pause capture for periods you do not want included.
Capture has to be active before the work you want to review. It cannot fill earlier gaps or measure work away from the Mac. Local model and Pro setup may need internet initially; the retained activity can be reviewed locally afterward.
Review a day or a week
- Open Reflect in OGAD.
- Select Day for one day's record or Week for the seven-day view.
- Use the date arrows to choose the period.
- Read Mind share — what you gave attention to, or Mind share — this week.
- Compare the named work areas, durations and percentages.
- Use Day → Timeline or Replay to inspect the underlying work context when an estimate looks surprising.
Work areas can be inferred projects, topics or people. They are not necessarily the same as the uploaded-file workspaces in the Projects sidebar. Do not assume every label is a clean, exclusive project code.
How is the time estimated?
For each observation, OGAD attributes the time until the next observation to that moment's area, with a maximum gap of five minutes. The last observation receives a 45-second tail. When an observation relates to several entities, its time is split between them rather than counted in full for each one.
Those rules limit how much a long gap can inflate the total, but they do not establish what you were doing during every gap. Paused capture and work away from the screen remain missing. A misidentified topic can also place time under the wrong label.
The weekly view adds the estimates from seven days. Read the selected period carefully rather than assuming it always means a Monday-to-Friday workweek.
Compare patterns before exact totals
Use the largest work areas to decide where to look more closely. Then inspect a few relevant timeline blocks. Does the project label describe what was actually on screen? Was a long research session useful to that project, or did the model associate it too broadly?
A useful planning note might be:
The captured record suggests that project A dominated this period. Project B appears in only a few short sessions. I will reserve a longer session for B next week and check the result again.
That is an interpretation you can verify and act on. Avoid converting the displayed estimate directly into an invoice or an assessment of someone's performance.
Make the next review more useful
Keep capture consistent during the periods you intend to compare. Note major gaps, such as a workshop away from the computer. Use the same kind of period for each review so a full week is not compared with a partly captured afternoon.
The goal is a clearer picture of your own work distribution. Exact client billing or contractual time reporting still needs a process designed for those requirements.
This guide follows the Mac Pro Reflect implementation associated with OGAD 0.0.51. It describes the current estimation rules without claiming a measured accuracy level.
Review one workday before changing the plan
Download OGAD for Mac, enable capture for a chosen work session and inspect Reflect afterward. Check a surprising result against the timeline, then use what you learn to plan the next session.
Top comments (0)