Project · Ops visibility

Agent work with a logged actual time: 0 to 16 of 16

  • Ops visibility
  • Internal system

Context

One operator ran several AI agent sessions at once. There was nowhere to record hours, no deadline field and no timeline. Agents finished work, but none of it carried an actual time. One morning automation run failed its own check and still reported success.

The decision

Keep reconstructing the day and the hours after the fact, or make every completed item log its own actual time and put deadline, estimate and actual on one page?

What was built

A Today page that lists every open item by deadline, with its estimate, a timer and manual time logging. A collapsible timeline. Hours reports by week or month with a billable export. Every item an agent completes now logs its actual time into a done-today list under the day totals. The morning automation run now records a failure as a failure. 99 tests were written to fail before the build, and 16 of 16 live checks on the running platform passed.

What it demonstrates

Time made visible rather than estimated after the event. Agent work that accounts for itself. Logged hours that feed billing directly. A failed run that can no longer pass as a success.

Reconstructed with synthetic data.

  • Role

    Designed and built

  • Stack

    React, TypeScript, Python, Flask, SQLite, Playwright, pytest

  • Duration

    23 to 24 September 2026

  • Outcome

    16 of 16 agent-completed items logged an actual time; 7 of 57 open items carry an estimate; failed runs reported as success 1 to 0

See the build, then book a call to talk through yours. Every engagement ends with a handover your team can run.