Automatism

A week of commits, tickets and meetings in. The hours nobody logged, out.

Watch Sipho's week at Northline Studio become suggested time entries. One overlaps time already billed to another client, so the rule trims it before Sipho reviews anything. This is a scripted replay on made-up data. The tool isn't built yet.

Unbilled time pipeline replay

45 seconds, no sound needed. Scripted demo on made-up data.

Step through it yourself

How the pipeline works

  1. Collect

    Reads the week's GitHub commits, Jira ticket activity, Google Calendar events and existing Harvest entries.

  2. Match

    Uses repos, ticket keys and meeting attendees to find the client and project. Private events stay out. Internal work stays non-billable.

  3. Find gaps

    Compares activity with existing Harvest entries for the same client and project. It finds 4.50 hours without matching entries. The cross-client time check comes later.

  4. Suggest

    Drafts a date, client, project, hours, note and source links for each possible entry.

  5. Guardrails

    Checks the source and existing Harvest entries. A 45 minute overlap on another client is blocked and trimmed, then checked again.

  6. Review

    Sipho checks and approves each corrected entry. The replay shows those approvals one by one.

  7. Log

    Adds only the approved entries to Harvest. Existing entries and invoices are untouched.

About this demo

Northline Studio, Sipho, both clients and all activity are made up. The same scripted run plays every time. It shows the intended workflow; the tool hasn't been built yet.

How does your agency catch unlogged time today?

If you found this through a post, reply there.