Guides

Planned vs executed RKM: reviewing the difference

Compare route measurements at the right level, keeping surveyed, executed and commissioned lengths distinct during rollout review.

By Lumacorp · Updated 14 October 2026

The same unit can describe different stages

A planned route length describes intended scope. A surveyed route describes what was captured. Executed length describes recorded delivery. Commissioned length refers to work that has reached the applicable commissioning stage. A kilometre total alone does not identify which stage it represents.

Match the scope before comparing totals

Confirm route boundaries, segment identifiers, units, measurement method and reporting date. A revised plan and an older field report may both be correct for their own scope while producing a misleading comparison.

Investigate at segment level

Locate the section responsible for a difference. Review the relevant field record and the reason for change. Check whether a discrepancy reflects missing work, a design revision, duplicate records or inconsistent scope before treating it as a delivery result.

Keep review distinct from payment

Mapped evidence can support billing verification. It does not, by itself, establish contractual acceptance or authorize a payment. The project’s review and finance processes determine how supporting records are used.

Document the review decision

Retain the identifiers and context needed to understand a reconciliation. Agree the actual status model and required supporting documents with your team. Avoid reducing the review to a number with no route or revision behind it.

Lumacorp tracks progress against route, segment and site context. Explore rollout and execution tracking to discuss your planned-versus-recorded review workflow.

Your network. Your next step.

See the workflow
with your project in mind.

Tell us what you need to capture, deliver or operate. We’ll start with the workflow that matters to you.

Book a demo