Colibrity work record

What that works out at

How the two lines moved apart

Value delivered and value charged, both counted in euro at the same an hour, month by month.

What each project worked out at, per hour

Each fixed price divided by the hours it actually took, against the rate agreed for support work. Shown because it is the clearest single measure of the gap.

What was delivered

Three sites. Two are finished, live and paid for; the third is finished and still open. Measured results, with the date each measurement was taken.

The toolkit you also got

not charged

What it is

When the work happened

Hours per month, by project. May and June are the two fixed-price builds running alongside each other; the tail from late July is support and the front-end standard.

How the hours were counted

Two records, reconciled day by day. Where the time tracker has an entry for a day, its wall-clock figure is the one used; where it has none, the session log's active-hours estimate stands in.

The time tracker's total is the figure of record: across days it logged to this client, inside working days in all.
A day split across two projects is divided by that day's share of work, not assigned whole to one of them.
Research, testing and measurement runs, deploys, calls and written reports are only counted where they left a record. A good deal of the work does not appear in the commit counts at all.
The tracker's own report reads 498:56:43. Its CSV export sums to 497:36:43 over the same days, a difference of exactly 1:20:00 that I have not been able to account for. The report figure is the one used here, and the difference is left standing rather than adjusted away.