Active vs non-active counting & logging · commented 25 September 2026 · nothing built yet

Live Project — the task list

Everything the document asks for, written as tasks. It covers when a capturer counts as actively capturing, new defaults for the pace settings, and changes to the top bar, the Team Performance panel, the capturer card and the capturer detail. Most of the asks are comments pinned to screenshots, so each group shows the screenshot with its comments under it.

Tasks
31in six groups
Comments
1510 pinned to screenshots
Removals
7and one chart replaced
Open questions
105 in the doc, 5 from the comments
the direction

Speed is measured against active time only, and the screens get simpler. A pause of more than 5 minutes is a break, with no pace multiplier and no room-change rule. A day ends when the team presses We are done, or once every room is complete, processing has finished and an hour has passed. The capturer detail loses its repeated tiles and gains an idle-time split and a line chart.

When someone is not countinganalytics · T1–T5

The document lists these as a chain: each step needs the one before it. A capturer is not actively counting while any of them holds.

  1. T1Not counting until they are set up: the app is open, a facility is chosen, Add Inventory is selected, and a floor, department and room are chosen.rule
  2. T2Not counting in a room when the camera has been idle for 1.25 min, or there have been no captures for 5 min.1.25 min is marked as a placeholder (Q9).rule
  3. T3Allow their breaks: a 45 min lunch, a 15 min break and a second 15 min break.rule
  4. T4Don’t hold audit time against them: each person is audited 5 times, and they may sit on the camera screen while the supervisor audits on their own phone.The sentence in the document stops half way (Q8).rule
  5. T5Not counting while they are on the Audit screen.rule
mostly phone-side

App open, camera idle, the Audit screen, a locked phone, another app, a phone call — only the phone knows these, so this group needs the mobile app to report them, not just the web dashboard. The document leaves five questions about it open: Q1–Q5.

New settings defaultspace settings · T6–T13

The screenshots show the settings with new values typed over the current defaults, marked Custom. The comments say which to keep and what to drop.

Breaks inside a room5 min typed over the 10 min default

Settings card Breaks inside a room: Pause is a break after, set to 5 min against a 10 min default, and ...and longer than, 5 times the usual time per line
Breaks inside a room — as it is today
on the screenshot above

5 minutes and REMOVE ...and longer than

Peter Stahl · 25 Sep · C0
  1. T6Set “Pause is a break after” to 5 min by default (now 10 min).change
  2. T7Remove the “…and longer than N × line” setting. A pause of more than 5 min is a break, whatever the person’s usual pace.remove

Room changesboth settings go

Settings card Room changes: Room change holds a break after, set to 5 min against a 15 min default, and ...and longer than, 3 times the usual walk
Room changes — as it is today
on the screenshot above

Can be removed bc its redundant of the first one - we don’t care what they are doing during their “break”

Peter Stahl · 25 Sep · C1
  1. T8Remove the Room changes card and the rule behind it. The in-room rule (T6) covers it.remove

End of day & datatoday a day ends after 60 min with no captures

Settings card End of day and data: Day ends after no captures for 60 min, and Captures needed before showing pace, 5 gaps
End of day & data — as it is today
on the screenshot above

1. There should be a We are done button on Dashboard somewhere

- no processing / WR done becomes UN GRAY when processes are completed and ready for reporting

2. All rooms market completed, no processing / WR done AND 60 minutes have passed

Captures Needed before showing pace change to 12

Peter Stahl · 25 Sep · C2
  1. T9Add a We are done button on the dashboard. It stays greyed out until nothing is still processing and WR is done, so the data is ready for reporting.Per capturer or per project is open (Q6).add
  2. T10End the day automatically once all rooms are marked complete, nothing is processing / WR is done, and 60 minutes have passed. This replaces “60 min with no captures”.change
  3. T11Set “Captures needed before showing pace” to 12 (now 5).change

Verdicts1.25×, 0.75× and 95% typed over 1.1×, 0.9× and 90%

Settings card Verdicts: Ahead when faster than 1.25 times the median, Speed up when slower than 0.75 times the median, Slow down when audits pass below 95 percent
Verdicts — as it is today
on the screenshot above

Update the #s and for audits - If they miss 2 then vs slow down - Schedule check-in on quality concerns

Peter Stahl · 25 Sep · C3
  1. T12New verdict defaults: Ahead above 1.25 × median (now 1.1), Speed up below 0.75 × median (now 0.9), Slow down when audits pass below 95% (now 90%).change
  2. T13When a capturer fails 2 audits, show “Schedule check-in on quality concerns” instead of “Slow down”.How this sits with the 95% rule is open (Q7).add

Top barlive project tab · T14–T18

The Live Project tab header: Live capture in progress, Day 1 of 1, 0 capturers on-site, a progress bar with 3 of 9 locations complete, 136 captures, 1,212 EA total, 70 SKU, 6 remaining, 33% Complete and a Projected finish box
Top bar — as it is today
Crop: Day 1 of 1, 0 capturers on-site
T14 — 0 on-site
Crop: 33% Complete and Projected finish, Not enough capture yet
T15–T16 — both go
Crop: the stats line under the progress bar
T17 — the line that changes
  1. T14Bug: “0 capturers on-site” should read 4.Cause: the count keeps only people whose last capture was within the 60-minute day-end limit. The fix counts today’s roster — see the top bar fix.bug
  2. T15Remove “33% Complete”.remove
  3. T16Remove “Projected finish”.remove
  4. T17Replace the stats line with:
    0 of 1 departments complete | 3 of 9 locations complete | 136 captures | 70 SKUs | 1,212 EA | 2 of 4 Audits passed | 16 Audits pendingNew: departments complete, audits passed, audits pending. “6 remaining” goes, and SKUs move ahead of EA.    change
  5. T18Work out “Audits pending” from the team: every person needs 5 audits for GHX.In the example: 4 people × 5 = 20 needed, 4 done, 16 pending.add
on “16 Audits pending”

Dynamic - Every person requires 5 audits for GHX

Peter Stahl · 25 Sep · C4
fix written up · not applied yet

How each number in T14–T18 is worked out, and the exact patch for the API and the app: Top bar fix.

Team Performance panelT19

Team Performance panel with four capturer cards; the header reads Expected median 8, Actual median 6.1 captures per minute
Team Performance — as it is today; the header text is highlighted
  1. T19Add team speed to the panel: 17 captures / min – 1,020 captures projected per hr, a trend that rolls up the individual speeds.Team speed is the sum of each person’s captures per minute (8.4 + 6.1 + 2.9 ≈ 17). Per hour is team speed × 60, worked out live. It probably takes the place of the highlighted “Expected median 8 · Actual median 6.1”.add
on “Team speed 17 captures / min”

Sum of team members per min metrics

Peter Stahl · 25 Sep · C5
on “1,020 captures projected per / hr”

17 x 60 min - dynamic

Peter Stahl · 25 Sep · C6

Capturer cardone per person · T20–T23

One capturer card: Speed 8.4 captures per minute, Audit 1 of 2, Today 44 captured, On-site 0.1 hrs
Capturer card — today: Speed, Audit, Today, On-site
  1. T20Reorder the tiles: Speed, Captures, On-site, Audit.change
  2. T21Speed tile: change the text so it reads as active counting speed.No exact wording given.change
  3. T22Rename “Today” to Captures, shown as “44 today”.change
  4. T23On-site tile: show hours actively capturing against total hours.Every speed number is measured against active time. The Audit tile stays as it is.change
on “Active hours capturing* vs total hours”

All metrics on speed are held against ACTIVE

Peter Stahl · 25 Sep · C7

Capturer detailopens from a card · T24–T31

The capturer detail titled Speed - Ishita Chakravarthy: date, first and last capture, On floor 0.1h of 8h scheduled, Finished badge, four tiles, Where the time went, Breaks, Rooms worked and Speed by hour
Capturer detail — as it is today
  1. T24Title: drop “Speed -” and show only the person’s name.change
  2. T25“On floor 0.1h of 8h scheduled”: make it clear whether that is active hours or total hours.change
on “On floor”

Make this easy to understand if its active hours vs total hours there

Peter Stahl · 25 Sep · C8

Tiles and time barboth go

Four tiles: Speed 2.9 captures per minute, Active 0.3 h, Captures 44, Breaks 0
The four tiles
on the screenshot above

Remove - Redundant of 1st screen

Peter Stahl · 25 Sep · C9
Where the time went: a bar split into Counting 12m, Walking 3m and Breaks 0m
Where the time went
on the screenshot above

Remove

Peter Stahl · 25 Sep · C10
  1. T26Remove the Speed, Active, Captures and Breaks tiles. They repeat the capturer card.remove
  2. T27Remove “Where the time went”.remove

Breaks become idle timeand the empty section needs an answer

Breaks section reading No breaks detected this day
Breaks — empty on this day
on the screenshot above

Change word from breaks to Idle time

-Lunch - Longest/max unique break

-Scheduled Breaks - 2nd Longest + 3rd longest SUM

-Other - All other breaks SUM

Peter Stahl · 25 Sep · C11
on the screenshot above

Where. did the break data go?

Peter Stahl · 25 Sep · C12
  1. T28Rename “Breaks” to Idle time and split it into three lines: Lunch — the longest single break; Scheduled breaks — the 2nd and 3rd longest, added together; Other — all the rest, added together.change
  2. T29Find out why the section says “No breaks detected this day” and answer “where did the break data go?”Check it against the current thresholds before treating it as a bug.answer

Rooms workedtwo things go

Rooms worked table: PACU 10:30 to 10:36, 5m counting, 42 captures, 8 per minute; Office 10:39 to 10:46, 7m counting, 2 captures
Rooms worked
on the screenshot above

Remove 5m counting

remove captures/min column

Peter Stahl · 25 Sep · C13
  1. T30Remove the “5m counting” line under each time, and the Captures/min column.remove

Speed by hourreplaced by a line chart

Speed by hour: one bar for 10:00 AM with 44 captures at 2.9 per minute, and a note on the break rules under it
Speed by hour — and the rule note under it
on the screenshot above

Remove and replace

Peter Stahl · 25 Sep · C14
  1. T31Replace “Speed by hour” with a line chart: time on-site along the X axis, capture velocity up the Y axis, and the line turns yellow during idle time.The note under it quotes the old 10 min and 15 min rules, which T6–T8 retire.change

Questions to settlebefore building

Q1–Q5 are asked in the document and left open. Q6–Q10 come from reading the comments.

  1. Q1Does a locked phone count as not counting?
  2. Q2Does having another app open count?
  3. Q3Does a phone call count?
  4. Q4How is sync factored in?
  5. Q5How is offline mode factored in?
  6. Q6End of day (T9–T10): is “We are done” for each capturer, or for the whole project or day? What exactly counts as “processing / WR done”?
  7. Q7Audits (T12–T13): does “fails 2 audits” replace the 95% rule, or apply alongside it? Is “Schedule check-in on quality concerns” a verdict label or the note under the card?
  8. Q8Audit time (T4): “Audited 5 times … so” ends half way. What was the rest?
  9. Q9Camera idle (T2): 1.25 min is marked as a placeholder. What is the real number?
  10. Q10Audits pending (T18): is 5 audits per person only for GHX, or for every client?