Pathfinder Sustainability

The problem

A stack of invoices shows what arrived. It cannot show what did not. Pathfinder is designed to look for both.

Status: planned. Pathfinder is at design and specification stage. Nothing is live yet.

Illustration: Paper marks arrive along tangled route lines and settle into a ruled grid of vendors and periods, cell by cell. One cell stays empty while the others fill. A dashed outline appears around the empty cell and it is labelled Missing. A metaphor for a missing invoice, with no real data.

The invoice that never arrives

A missing invoice leaves no page to read. It only shows when someone compares what arrived with what was expected.

Pathfinder is designed to make that comparison for every delivery, by vendor, property and month, against the services the client expects at each of its properties. An invoice that should have arrived and did not is listed as missing.

Illustration: A grid with vendors along one side and months along the other. Marks drop into their cells. The cell where nothing lands is outlined and labelled Missing. The vendors and months are invented.

A problem needs an owner

A missing or problem invoice is designed to become an exception. That is a record with an owner, a reason, an age and a target for closing it, worked in one place.

It does not stay a silent gap.

Illustration: A flag on a survey stake, with a tag tied to it. The tag has three blank fields, Owner, Reason and Age. A route line leads from the flag to a person's mark. A metaphor for an exception record. No values are shown because none are real.

The other end of the route

What a client is designed to see, once the checks are done.

Last reviewed .