# Trace missing values

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Trace missing values

ID: MHC-D-RESEARCH-9723 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/trace-missing-values

One percentage can hide where values disappear.

Knowledge source release: MHC-RPUB-20261112-20287590
Source corpus commit: 20287590ddd3999b7492df232822b6a0f7d114b1
Source manifest SHA-256: 2a987660d12de0ce2bde77a421424f7762af1ff77872ef41093fecc33db74a95
Source projection SHA-256: 2807da39bbe6a3dee2db32a76675ac5185f5a33e8b0a5cdd0c22a4731f3378a0

### Use when

- A column has many blanks after merging several upstream feeds.

### Avoid when

- Scattered blanks do not prove that values are missing at random. Filling a blank does not confirm why it was empty.

### Explanation

Count missing required values by source, period and record type, using explicit rules for fields that do not apply. Trace relevant records from raw input through the processing steps. Mark each explanation as confirmed or unconfirmed; grouped rates alone do not tell you why a field is blank. Choose a fix only when the evidence supports it.

### Steps

1. Report missing and eligible counts for relevant groups.
2. Compare input and output for relevant records.
3. Separate confirmed non-applicability from unexplained missing values.

### Example

Suppose two feeds each supply 100 accounts. All 100 from A have blank country codes after loading; none from B do. The overall 50% missing rate hides a feed-specific gap. Comparing raw input and output can help locate it.

### Check

The report separates counts, confirmed explanations and open questions, with a justified follow-up or an explicit decision to take no action.

### Limits

- Scattered blanks do not prove that values are missing at random. Filling a blank does not confirm why it was empty.

### Evidence and sources

- supports: The guidance recommends reporting reasons for missing important data, distinguishing fields that intentionally do not apply, and investigating whether data errors are systemic or arise from a one-off event. — gov-guidance. Claim limit: Grouped missing-value counts and input/output tracing are authored diagnostic adaptations. The selected guidance does not make a visible pattern proof of a cause, nor establish random missingness when no pattern is visible.
Source reading history: selected_passages; 2026-10-11; Data quality action planning steps 1–3 and 8; previously selected metadata and quality communication guidance. Official page was opened on 2026-10-10 and identified sections inspected. This verifies a narrow reference basis, not the effectiveness or completeness of independently drafted practice steps. On 2026-10-11 action-planning steps 1–3 and 8 were read again for card 9721; this is selected-passage screening, not independent review. On 2026-10-11 the Completeness communication section, action-planning step 7 and root-cause data-journey section were read again for the missingness correction; source screening only.
Agent release review: PostgreSQL 18 table expressions, NULL comparisons and aggregates, the UK Government Data Quality Framework and Microsoft Power Query profiling documentation were checked at the cited sections. The original examples and scope limits remain attached. (Communicating data quality to users: Completeness; Data quality action planning, step 7; Root cause analysis, Understand the data journey)
- gov-guidance: The Government Data Quality Framework: guidance — https://www.gov.uk/government/publications/the-government-data-quality-framework/the-government-data-quality-framework-guidance

Review: agent · Agent editorial and scoped source review · 2026-11-12T18:37:40Z
Published: 2026-11-12T18:37:40Z
Related (use_before): https://vedokrok.com/knowledge/give-a-data-defect-an-owner
