Built by a planner, for the checks planners actually do.

Placeholder copy in the founder's voice. Edit it, and replace the bracketed details, before launch.

I've spent 25 years planning construction, rail, offshore and energy projects, [FORMER EMPLOYERS OR PROJECTS, IF YOU WANT TO NAME THEM]. For most of that time, checking a programme meant the same routine every period: export it, count open ends and constraints in a spreadsheet, and hope nothing important slipped through.

The programmes that went wrong rarely failed on something clever. It was a hard constraint hiding negative float, a stale schedule run, a critical path that didn't reach the finish. Things a client, a Project Manager or a delay expert would find in minutes, once they looked.

So I built the tool I wanted to use: one that reads the XER, checks it the way it will be checked, and shows the activities behind every finding. It recomputes the critical path rather than trusting stored float, because the difference between the two is usually where the problem is.

Every check in it was verified against hand-worked answers and real programmes. When a result looked wrong, the rule was changed, not the result.