Setup checklist: draw the branches first
Sketch the form on paper before configuring conditions. A client choosing a video request may need a reference file and target duration; a static graphic may need dimensions instead. ManyRequests documents show-and-hide rules for request forms. That capability helps reduce clutter, but a complicated tree can also hide essential questions. Start with a small number of meaningful branches tied to genuinely different production requirements.
Keep shared fields outside the branches
The objective, deadline and approver may apply to every request. Repeating them inside each branch makes future changes harder to maintain and can create inconsistent wording. Keep a simple list of shared requirements and branch-specific ones. If a field appears only after a particular answer, explain why it matters. A customer should not have to guess which selection unlocks the place to provide an important constraint.
Test changes of mind
Use fictional answers to select one request type, fill its fields and then switch to another type. Inspect what remains visible and what reaches the submitted record. Do not assume hidden fields are erased or ignored unless the supported behavior is verified. Check missing and contradictory inputs too. This exercise is an acceptance method for your configuration; it is not a claim that we have tested the vendor’s form implementation.
Maintain a branch owner
Give the form a version and a person responsible for updates when the service changes. Keep the prior brief with existing work rather than applying new questions retroactively. If a branch exists only for a rare exception, a short manual clarification may be simpler than permanent complexity. The right form is the smallest one that produces usable briefs reliably, including on a phone and for a client encountering the service for the first time.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- ManyRequests conditional request fields — Merchant documentation · help.manyrequests.com · Merchant-controlled · checked 2026-09-19
- ManyRequests service request forms — Merchant documentation · help.manyrequests.com · Merchant-controlled · checked 2026-09-19