How to define required fields before connecting a request form

REQUEST INTAKE FIELD AGREEMENT
Workflow / receiving step / owner:
Field name / person or system that supplies it:
Why the next step needs this field:
Required or optional:
Type / format / allowed values / limits:
Absent / empty / null / zero / false behavior:
Permitted conversion and its exact boundary:
Valid example / invalid example / expected correction:
Separate catalog or permission check:
Error message / restricted evidence / correction owner:
Contract version / review date:

CHECK BEFORE CONNECTING
[ ] The receiving team agrees the required fields.
[ ] Browser and receiving checks use the same contract.
[ ] Identifiers keep their intended characters.
[ ] False and zero follow field-specific rules.
[ ] Invalid requests cannot reach the action step.
[ ] Exceptions have a correction owner.
[ ] Synthetic cases have observed results recorded.
[ ] The current contract version is in the handoff.

ZenOut Labs | https://zenoutlabs.com/guides/request-intake-required-fields/