Reviewing suggestions
Approve, edit, or dismiss the time ProjectPacer spots — and why a suggestion might not appear at all.
Suggestions collect on the AI suggestions screen (the sidebar shows a count when there's something to look at). Each one is a proposal, never a done deal — you decide what happens.
Two ways to review: List or Timeline
A toggle at the top of the screen switches how the same suggestions are laid out. Pick whichever fits the moment — it remembers your last choice.
- List groups suggestions by kind — missed time, overruns, wrong-project fixes, duplicates, and so on — each in its own collapsible, color-coded card. Best for clearing a backlog one type at a time.
- Timeline lays out your day in time order, each suggestion sitting where it belongs: a missed-time window in the gap between two entries, a trim drawn on the entry it shortens, a switching gap between the two blocks it bridges, a meeting to log at its slot. Your tracked entries show alongside for context, and a now line marks the present moment. Best for reviewing recent days in context. A handful of suggestions aren't tied to a spot on the clock — a duplicate, a wrong-project fix — so those collect in an Also list beneath the day.
Both views share the same header (the time captured this month, and Refresh), and every action behaves identically in either. The Timeline only shows days that actually have something to review — a day of nothing-but-tracked-time won't clutter it.
Three things you can do
Accept the suggestion and it becomes a real time entry on the project shown.
Adjust the project, description, or times first — a meeting titled "Sync" might belong on a different project than its name implies. Then log it.
Not billable, not real, or already handled? Dismiss it and it stays gone — you won't be shown the same one again.
When a Missed time window reaches the present moment — you've been working without a timer and you're still at it — it also offers Start timer. That starts a live timer backdated to when the work began, so your elapsed time is already correct and keeps counting, instead of logging a closed block you'd have to reopen. (Starting it stops any other running timer, since only one runs at a time.)
How a work window becomes suggestions
Missed time reconstructs the windows you were working — bounded by your activity: the desktop app waking then idling or locking, a stretch of Slack presence — and splits each into a suggested entry per project, using your work markers inside it (a commit, a Slack message you sent, a task you moved). Two commits on different projects an hour apart become two entries, split at the switch; several on one project merge into one stretch. When a window holds more than one project it shows as a grouped card — log it segment by segment, or the whole window at once.
Every suggestion is tagged with how sure we are:
- Confident — a work marker attributes it, so we know what you were on. On by default whenever Missed time is.
- Likely / unconfirmed — a presence signal shows you were at your desk, but nothing says on what. Off by default: turn on Also flag desk time with no work artifact (under the Missed time type in Settings → AI suggestions) to catch these too. These follow your actual activity — any hour, any day, not just your working hours — with the project estimated from nearby work.
The project on every suggestion is a starting point — from a marker when there is one, otherwise from the work bracketing it. You confirm it, and can change it in the editor, before anything is logged.
Why a suggestion might not appear
A suggestion only shows up when its source is connected and its type is switched on. So an empty screen can mean you're all caught up — or that the source or toggle isn't on yet. Check Settings → AI suggestions: source-driven ones (missed time, overrun, entry fixes, split time) need a source; the rest run on your existing entries. Anything you've turned off there simply won't surface here — as will anything an admin has switched off for the whole workspace, which that screen tells you.
Grouped by kind (List view)
In the List view, suggestions are grouped so you can work through one type at a time — missed meetings, overruns, wrong-project fixes, split-time carves, duplicates, overlaps, and short switching gaps. Each group is a color-coded card you can collapse; the same colors carry over to the Timeline. Turn any group off entirely from settings if it's not useful to you. Entry fixes (move a whole entry) and Split time (carve a multitasked block into pieces) are separate toggles, so you can keep one without the other.
The Overrun group covers two things: a finished entry whose end ran past your last activity (one tap trims it), and a still-running timer that's gone idle — it offers to stop it at your last activity. How soon that live nudge appears depends on how much we can see: a lock or sleep bookending your last action (you clearly stepped away) triggers it fastest, and the more sources you have quietly agreeing you've stopped, the sooner it fires. If your calendar is connected, a live meeting holds the nudge back — you're legitimately away from the keyboard — and outside a meeting it leans in a little sooner. It clears itself the moment you're active again, and if a timer sits idle for hours the fuller timer-left-running review takes over instead.
ProjectPacer never logs, edits, or deletes an entry by itself. Every change to your timesheet passes through your review here.
See the evidence behind a suggestion
Want to know why a suggestion picked a particular time? Turn on Settings → AI suggestions → Presentation → Show the evidence behind suggestions. Each overrun and left-running-timer suggestion then gets a “why?” — expand it to see your last activity per source (desktop lock, in-app action, a commit, a meeting's end) and pick a different stop time if one fits better. It's times only, never what's on your screen, drawn from the sources you connected, and only you can see it.
Missed time gets the same treatment: a Why line showing what put the segment there (a commit, a Slack message sent, a task moved, time at the keyboard — with counts and times). A calendar meeting needs none of this — the invite already says what it is — so those carry no evidence.
Sources, privacy, and the bigger picture.