Work through the decision
Record each activity’s stable identity, quantity, unit, time period and measurement or estimation basis. Connect it to the project, asset or batch. Distinguish intended deployments and estimated journeys from observed use, receipts or treatment. Review duplicates and shared allocations so one underlying activity does not increase totals from two brand views.
A fictional worked example
A fictional equipment booking appears in both related platforms. The learner links both views to one deployment ID. Only the actual observed use enters the achieved ledger; the duplicate view and future booking do not add further events.
Evidence and authority limit
A spreadsheet row or calendar date is not independent proof that the activity occurred.
Put it into practice
Enter one planned journey and one observed deployment with explicit source and units.
Keep this record: An activity input register with basis, dates, provenance and duplicate checks.
- Quantities have explicit units.
- Planned and observed activity are separate.
- One physical activity is counted once.
.jpg){kind=link}