Timecard Visualization Service

How it works

No hand-classification, no separate approval workflow. One flag per timecard entry, set at the source, drives the whole breakdown.

1. 01Input

   Every timecard entry carries a work type and an hours split

   Each row is one person, one entry: how many hours were reported, how many of those were realized (billable, on a completed job), and a flag for whether the remainder was necessary but not billable, or pure overhead.

2. 02Rollup

   Hours roll up into three buckets

   Realized time adds to the Realized bucket. The rest splits by that one flag: Utilized for necessary-but-not-billable work, Reported for everything else. That three-way split is the whole idea; everything downstream is just ways to look at it.

3. 03Sunburst

   A sunburst renders a crew's week at a glance

   Work-type leaves nest under each bucket, sized by hours. The real service has three variants of this chart, from a plain two-ring version up to one that breaks each bucket down by job code, for when you need to see which project actually ate the week.

4. 04Variance

   A companion chart compares worked vs. estimated hours

   Per job phase, the taller of worked/estimated draws first and the shorter overlays on top, so a phase running over budget reads as an obviously mismatched pair of bars rather than a table you have to do the subtraction on yourself.

Why a sunburst at all: a table of hours by work type answers "how much"; nesting work types under Realized/Utilized/Reported answers "how much, of what kind" in one shape, which is the actual question an ops manager has when they open this.