A dictionary for your columns — Everyday Platform

A field name is often an abbreviation for a longer idea. Different readers may interpret “active,” “complete,” or “value” differently unless the rule behind the field is written down.

Create a small data dictionary with the meaning, unit, allowed format, and important exclusions for each column. Include an example where it helps. The description should reflect the actual collection process, rather than an ideal definition no one follows.

Update the dictionary when a field’s meaning changes. A historical table may need the earlier definition preserved too. Clear column definitions make analysis, sharing, and future corrections easier to discuss.

A small working example.

Consider handing over a table with a special code for unavailable values. Explain that code before someone mistakes it for an ordinary measurement.

A note to keep beside it.

Treat an unexpected value as the start of an investigation. Its source and context matter before you decide whether to remove it or build a story around it.

A few starting points