Who it is for
- Research teams screening participants
- Product teams recruiting interview candidates
- Programs checking eligibility before scheduling
Form template
Screen participants with consent prompts, eligibility criteria, demographic fields, scheduling preferences, and review notes.
Problem
A useful template has to capture the right details, guide respondents away from irrelevant fields, and leave reviewers with enough context to make the next decision.
The template outline combines field groups, conditional logic examples, validation checks, review handoff notes, and related pages so teams can adapt it without starting from a blank form.
Use cases
These examples keep the page focused on narrow form-workflow intent instead of broad form-builder copy.
Workflow steps
Use KinoForms to adapt the fields, logic, validation, access, and review steps for the workspace that owns this process.
Start with identity, contact, request, or eligibility fields that every respondent should complete.
Show extra fields only when an answer makes them relevant, such as approvals, availability, or budget detail.
Use required fields, option constraints, dates, and review-ready labels before the response reaches the team.
Concrete examples
The form only shows availability fields after the participant confirms consent.
Screening answers and reviewer notes stay in one record for scheduling decisions.
Phone follow-up can require a phone number and time zone, while video-call follow-up can collect availability windows.
Related pages
Build inclusion, exclusion, consent, and scheduling branches.
Review participant responses in a controlled workflow.
Separate research projects and participant queues by workspace.
Validate consent, contact, and eligibility fields before scheduling.
FAQ
Include consent, contact information, eligibility questions, demographics, availability, and reviewer decision fields.
Yes. Conditional logic can hide scheduling fields or show alternate review notes when exclusion criteria match.
Next step
Use KinoForms to adapt the fields, logic, validation, access, and review steps for the workspace that owns this process.