Fixed intakeREVIEW FILES
Turn known fields into clean records
This shape fits a small contact or intake job with a fixed field set, clear validation, and CSV or NDJSON files for review.
Test the fixed-intake boundaryChoose the form job
Choose the Form Job Before You Choose the Form Tool
A five-field intake can become a payment, approval, document, and team-access project by the time someone presses Submit. Name what must happen after that click before you replace the tool around it.
One-question researchONE COMPLETED ANSWER
Define the answer before the interface
This shape fits one controlled prompt with a named answer type, affirmative consent, a completion rule, and one CSV row.
Test the one-question boundaryBusiness workflowCONNECTED OPERATIONS
Keep the system around the form
Payments, approvals, generated documents, regulated data, team routing, and connected applications make the surrounding service part of the result.
Follow the answer past Submit
Write every action that follows collection. A short list ending in review and export points to a smaller job. A chain of approvals, payments, notices, and shared access points to a wider system.
This check prevents a cheap form screen from inheriting duties it cannot finish. It also reveals when the costly platform surrounds a small job you can separate.
Use an inspectable result as the stopping point
The demonstrated intake job validates supplied fields and produces CSV and NDJSON files. The demonstrated survey job checks one supported answer, consent, completion, and a formula-safe CSV row.
Those files support review of the smaller jobs described here. They do not establish collection, payment, notification, or team behavior beyond the supplied records.
Use this rule
Choose the smallest boundary that completes the next handoff
Use fixed intake when known fields and review files finish the work. Use one-question research when one controlled answer is enough. Keep the wider service when the submission must trigger business operations.
Make the split