Keeping a Verification Dashboard Denominator Stable During Fieldwork
Show newly discovered assets and scope changes separately so verification dashboard progress remains understandable throughout a changing fieldwork project.
How should a dashboard handle assets discovered after verification begins?
Preserve the agreed baseline and report approved scope changes explicitly. Show baseline completion, newly discovered items and the revised total without quietly rewriting earlier results. Define what counts as completed and ensure each dashboard figure can be traced to a dated population and its underlying records.
A team starts with 1,000 expected assets and observes 600. It then captures 100 unlisted discoveries that remain unreviewed and unaccepted for completion. If the dashboard adds those discoveries only to the denominator, progress falls from 60 per cent to roughly 55 per cent without undoing any work. Before changing either side of the ratio, explain how discoveries enter the approved scope and completion count.
Name the baseline and completion rule
Assign the starting population a version, extraction date and scope description. Record included sites, asset classes and exclusions. Define completion in terms the project can apply consistently: an observation may be complete while a resulting ownership or data correction remains unresolved. Avoid one status that mixes physical coverage with exception closure.
Give the baseline a stable identifier in reports and exports. If records are later merged or corrected, retain the relationship to the original population so historical progress can still be explained. A dashboard should not depend on a mutable list whose previous contents cannot be recovered when management questions an earlier figure.
Treat discoveries as a visible scope movement
Place unlisted observations in a discovery queue with identifiers, location and review status. Check whether they are genuinely additional assets, duplicates of expected records or items outside the assignment. Do not immediately add every scan to the denominator; a visitor’s device or a duplicate tag may not belong in the project population.
When scope is revised, record the approved additions and removals with reasons and an effective version. Display the original baseline, the net change and the revised total. Separate unreviewed discoveries from accepted additions so a busy fieldwork day does not make the completion measure fluctuate according to raw capture volume.
Make historical figures reproducible
Store dated result snapshots or enough versioned data to reproduce each reported figure. Include the population version, completed unique items, open observations and unresolved exceptions. A reviewer should be able to drill from a percentage to the relevant records without inheriting today’s filters or scope changes accidentally.
When presenting trends, explain whether past percentages use their original denominators or have been restated to the current scope. Either approach needs a clear label. Add a short reason for significant changes so management can distinguish slower fieldwork, newly added sites and data corrections. The chart then supports decisions instead of rewarding silent removal of difficult assets.
Practical Example
Illustrative example: a project begins with 1,000 assets and completes observations for 600 of them. It captures 100 unreviewed discoveries, initially outside both the approved scope and completion count. Review identifies twenty duplicate observations of baseline items and eighty genuine additions whose evidence meets the completion rule. The dashboard retains baseline progress of 600 out of 1,000 and shows revised-scope progress of 680 out of 1,080. If evidence for any addition remained incomplete, that item would enter scope without entering the completed numerator.
Action Checklist
- 1.Save a dated baseline with included sites, classes and an explicit completion definition.
- 2.Review discoveries for duplication and scope before changing the expected population.
- 3.Display additions and removals as explained movements between population versions.
- 4.Retain the data and filters behind each percentage reported to management.
- 5.Label trend figures when historical percentages are recalculated on a revised scope.
For dashboards with traceable scope and completion measures, explore Asset Management Software.