Gen8

Installation contractor: weekly report from three sources

Case study · installation contractor (projects and on-site service work)

Reconciliation made visible instead of hidden

Compile a weekly operational overview from planning, time tracking and invoicing, showing differences between sources as a separate list.

Three dark green blocks merge into one large green area; a branch leads to a small orange square that deliberately remains separate.

Evidence status

Status: not yet approved for publication. Results on this page are only included with the customer's approval.

Starting point

Where it began

The pattern described by this case: three systems describe the same work from different angles. Planning says what was supposed to happen, time tracking what was done, invoicing what was charged. Anyone making a weekly overview exports all three and compares them — then spends most of the time explaining the differences.

What makes automation tempting is also what makes it dangerous here: a system that combines the three sources into one tidy number removes exactly the information the overview was meant to provide.

Approach

What we built

This type of workflow reads the three sources, compiles the overview and keeps the differences separate. The report has two parts: the figures the sources agree on, and a list of items where they diverge — with each source's value and a reference to the underlying record for every item.

That second list is the real product. A difference between planned and recorded hours is a signal about the work, not a report error. It should reach the work planner instead of disappearing into a total.

Control

Where people stayed involved

The workflow is read only. Nothing is changed in any of the three source systems; the report is derived and makes no corrections to the records. Resolving a difference remains human work, in the system where it belongs.

For each run, the log records which sources were read and when. This makes a report traceable: a figure that differs from what someone sees in a source system is almost always due to a different reading time, and without that detail the discussion goes on for a long time.

The underlying workflows are described under the weekly operations report and compiling management reports, with sector context under construction and logistics. Other cases follow the same structure.

Result

What it achieved

This customer has not yet approved the measurable outcome for publication. Once that happens, the results will appear here.

Does this look like your process?

Bring it to a conversation. We assess whether the same approach fits and where the differences lie.

  • Reply within one business day
  • No obligation