What's included

What gets tested

  • Field-level checks against the eCRF/aCRF specification — data type, format, required/optional status, and controlled terminology
  • Skip logic, branching, and visit-scheduling behavior walked through as a site user would actually encounter it
  • Full mock-subject test scripts run visit by visit, not isolated field-by-field clicks
  • Round-one issues logged, fixed, and confirmed closed in a dedicated round-two retest
  • Sign-off documentation tying each resolved issue back to the UAT plan's pass/fail criteria

Real scenarios, not just clicks

Testing walks through actual visit and form-completion sequences, not just individual field checks in isolation.