What's included

What the plan specifies

  • Range and format checks for every applicable field, defined against protocol-permitted values
  • Cross-form and cross-visit consistency rules, including date-logic and dependent-field checks
  • Required-field and missing-data logic, including how "not done" and "not applicable" are handled
  • Severity and query-text conventions for each check, so programming and site-facing messaging stay consistent
  • A clear boundary between what's built as an edit check versus what's covered by the Data Review Plan's manual review

The spec behind every check

Every rule in edit checks programming traces back to a line in the DVP — nothing programmed that wasn't agreed first.

Reviewed alongside data review

Developed in step with the Data Review Plan, so programmed checks and manual review cover the data without gaps or duplication.