How to use the Missing Data Report Generator.
Missingness has several forms: blank, null, placeholder and unavailable. Define which values count as missing before summarizing coverage.
Make the workflow fit your task.
Define missing values separately for each field, including empty strings, nulls and agreed placeholders. Count missing records and show percentages with denominators. Break down affected groups when useful, without assuming that missingness means zero or a negative answer.
- What you provide
- Table and required fields.
- What you get
- Missingness by field and affected records.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Email values are blank, unknown and alex@example.com; unknown counts as missing.
Completed example
Two of three records have missing email information under the stated rule.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should zero count as missing in a coverage report?
Only when the field definition explicitly uses zero as a missing-value code. Otherwise it may be a valid observation.
Why is the missing percentage unexpectedly low?
Check whitespace-only strings and placeholder spellings. Also confirm whether the denominator includes filtered or excluded records.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑