Simple template
Project request
Ready
100%
Request type
Budget estimate$4,500
Live response
Title
Launch page cleanup
Type
Design
Contact
Budget
$4,500
Templates
Templates for forms your team actually has to operate
Start from common team workflows, then adapt fields, validation, respondent access, conditional logic, and workspace ownership to the process in front of you.
Try the template behavior before starting from it
These are small form surfaces, not screenshots: change values and watch the respondent view update in place.
Dependency example
filterEnum in action
Applied rule
Saudi program options
Engine output
Allowed values
ScholarshipResearch grant
Respondent sees
Scholarship, with other program options removed from the select.
Template definitions with rules you can inspect
Each example below carries fields, schema, and dependency data together so the public template page shows the logic behind the respondent path.
Live template
Program application
Active rules
Scholarship requires transcript
show, setRequired, setDescription
Hide research plan outside grant path
hide, setOptional
Hide guardian contact for adults
hide, setOptional
Required now
Application typeApplicant countryApplicant ageTranscript
Hidden now
Research plan summaryGuardian email
Outcomes
- Transcript appears and becomes required only on the scholarship path.
- Research plan appears and becomes required only on the research grant path.
- Guardian email appears only when the age rule marks the applicant as a minor.
Inspect definition
{
"fields": [
{
"id": "applicationType",
"label": "Application type",
"kind": "select",
"options": [
{
"value": "scholarship",
"label": "Scholarship"
},
{
"value": "research",
"label": "Research grant"
},
{
"value": "event",
"label": "Event access"
}
]
},
{
"id": "country",
"label": "Applicant country",
"kind": "select",
"options": [
{
"value": "saudi",
"label": "Saudi Arabia"
},
{
"value": "uae",
"label": "United Arab Emirates"
},
{
"value": "global",
"label": "Global"
}
]
},
{
"id": "age",
"label": "Applicant age",
"kind": "number",
"min": 14,
"max": 80,
"step": 1
},
{
"id": "transcriptUpload",
"label": "Transcript",
"kind": "file",
"accept": ".pdf,application/pdf"
},
{
"id": "researchPlan",
"label": "Research plan summary",
"kind": "textarea",
"placeholder": "Summarize the research plan"
},
{
"id": "guardianEmail",
"label": "Guardian email",
"kind": "text",
"placeholder": "[email protected]"
}
],
"schema": {
"type": "object",
"required": [
"applicationType",
"country",
"age"
],
"properties": {
"applicationType": {
"type": "string",
"enum": [
"scholarship",
"research",
"event"
]
},
"country": {
"type": "string",
"enum": [
"saudi",
"uae",
"global"
]
},
"age": {
"type": "number"
},
"transcriptUpload": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string"
},
"size": {
"type": "number"
},
"type": {
"type": "string"
}
}
},
"researchPlan": {
"type": "string"
},
"guardianEmail": {
"type": "string"
}
}
},
"dependencyData": {
"version": "1.0.0",
"rules": [
{
"id": "scholarship-documents",
"name": "Scholarship requires transcript",
"when": [
{
"field": "applicationType",
"op": "eq",
"value": "scholarship"
}
],
"enforce": [
{
"target": "transcriptUpload",
"action": "show"
},
{
"target": "transcriptUpload",
"action": "setRequired"
},
{
"target": "transcriptUpload",
"action": "setDescription",
"description": "Required only for scholarship applicants."
}
]
},
{
"id": "non-scholarship-documents",
"name": "Hide scholarship documents for other paths",
"when": [
{
"field": "applicationType",
"op": "neq",
"value": "scholarship"
}
],
"enforce": [
{
"target": "transcriptUpload",
"action": "hide"
},
{
"target": "transcriptUpload",
"action": "setOptional"
}
]
},
{
"id": "research-plan",
"name": "Research grant requires a plan",
"when": [
{
"field": "applicationType",
"op": "eq",
"value": "research"
}
],
"enforce": [
{
"target": "researchPlan",
"action": "show"
},
{
"target": "researchPlan",
"action": "setRequired"
}
]
},
{
"id": "non-research-plan",
"name": "Hide research plan outside grant path",
"when": [
{
"field": "applicationType",
"op": "neq",
"value": "research"
}
],
"enforce": [
{
"target": "researchPlan",
"action": "hide"
},
{
"target": "researchPlan",
"action": "setOptional"
}
]
},
{
"id": "minor-guardian",
"name": "Minor applicants need guardian contact",
"when": [
{
"field": "age",
"op": "lt",
"value": 18
}
],
"enforce": [
{
"target": "guardianEmail",
"action": "show"
},
{
"target": "guardianEmail",
"action": "setRequired"
}
]
},
{
"id": "adult-guardian-hidden",
"name": "Hide guardian contact for adults",
"when": [
{
"field": "age",
"op": "gte",
"value": 18
}
],
"enforce": [
{
"target": "guardianEmail",
"action": "hide"
},
{
"target": "guardianEmail",
"action": "setOptional"
}
]
}
]
}
}Focused pages for narrow form intent
Client intake form template
Collect client contact details, project goals, budget, timeline, qualification notes, and any private files required before the first call.
Vendor onboarding form template
Standardize vendor details, service categories, contacts, conditional document requirements, compliance-adjacent notes, and internal approval routing without claiming certifications.
Application review form template
Capture applicant profiles, program preferences, eligibility answers, private supporting documents, and reviewer notes for scholarship, program, or grant-style workflows.
Research screening form template
Screen participants with consent prompts, eligibility criteria, demographic fields, scheduling preferences, and review notes.
Event registration form template
Publish registration forms with attendee details, ticket preferences, dietary needs, guest sections, and confirmation fields.
Internal request form template
Route internal work requests with request type, priority, owner, due date, budget details, conditional attachments, and approval fields.
Problem
Generic templates do not explain the workflow behind the form
A useful form template should describe who it is for, which fields belong in it, how the respondent path changes, and how submissions move into review.
Template pages built around narrow intent
Each KinoForms template page includes the field outline, conditional logic examples, validation and review notes, related internal links, and visible FAQ content.
- Client intake form
- Vendor onboarding form
- Application review form
- Research screening form
- Event registration form
- Internal request form
Where this page fits
These examples keep the page focused on narrow form-workflow intent instead of broad form-builder copy.
Qualify client requests before a first call
Plan vendor details and document requirements
Screen program applications
Route internal work requests
How the workflow moves
Open a focused template page to see field groups, logic examples, validation notes, related routes, and FAQ content.
1
Choose the closest template
Start from the template page that matches the respondent and review workflow.
2
Adapt fields and logic
Change the field list, conditional sections, validation rules, and review handoff for the workspace.
3
Publish and review
Use the template as a launch point for a public or protected form with review-ready submissions.
What this looks like in a form
Client intake to proposal
Collect project details, budget, timeline, and qualification notes, then request private supporting files only when the workflow needs them.
Research screening to scheduling
Use eligibility rules and availability fields to decide which participants should receive follow-up.
Follow the connected form workflow
client intake form template
Plan project requirements, budget, conditional private attachments, and next-step context.
vendor onboarding form template
Plan vendor details, document requirements, approval notes, and review context.
application review form template
Plan applicant data, eligibility, document requirements, and reviewer notes.
research screening form template
Screen participants with consent, eligibility, scheduling, and reviewer notes.
event registration form template
Collect attendee, guest, session, and special request details.
internal request form template
Route team requests with priority, owner, budget, and approval fields.
conditional logic form builder
Learn how template fields can branch based on earlier answers.
form builder
Build the fields, sections, validation, and workflow rules behind each template.
form submission validation
Validate required template fields and conditional requirements before review.
controlled form submissions
Keep submitted template responses tied to validation and review context.
role-aware form access
Separate team, workspace, respondent, and integration boundaries for templates.
Common questions
Are KinoForms templates fixed forms?
No. The pages describe reusable workflow outlines that teams can adapt with their own fields, logic, validation, and review steps.
Do template pages include conditional logic examples?
Yes. Each focused template page includes visible conditional logic examples and matching FAQ schema.
Pick a template and adapt the workflow
Open a focused template page to see field groups, logic examples, validation notes, related routes, and FAQ content.