Request form templates

Streamline inquiries with our request form templates. Whether it’s service requests or employee and product queries, our templates are made for your needs.

StatFigure
Total request form templates14
Most-used templateClient intake form
Short form completion rate
(1-10 questions)
99.0%
Medium form completion rate
(11-20 questions)
95.7%
Long form completion rate
(21+ questions)
80.1%
Overall completion rate96.6%
Average question count8.1

Short request forms on this platform complete at 99.0%; once they pass 21 questions, that figure falls to 80.1%. The length of the ask, not the topic, decides whether the work starts. A request form collects the information you need from a person or team in one structured intake, so the work can move forward without a chain of follow-up emails. These 14 templates cover the most common asks: client onboarding, time-off requests, change requests, support tickets, and more.

The SurveyMonkey Forms product handles the mechanics that make intake reliable: typed fields, conditional logic, required fields, file upload, routing and notifications, approvals, integrations, branding, and embedding. Conditional logic shows or hides fields based on earlier answers, so a submitter only sees what applies to them. Required fields block submission until the essentials are filled in, which closes the most common failure mode, an incomplete intake that bounces back to your inbox.

At 8.1 questions on average, most forms in this category sit comfortably in the short band that completes at 99.0%. Routing then sends each finished submission to the right person automatically, so a request does not stall in a shared inbox.

  1. Start from one of the 14 templates on this page, or open the client intake form template for the most common setup.
  2. Add the fields you need, choosing from text, multiple choice, dropdowns, date pickers, rating scales, and file upload for supporting documents.
  3. Mark required fields for any information you cannot start work without, so nothing submits half-finished.
  4. Add conditional logic to reveal follow-up fields only when an earlier answer makes them relevant.
  5. Set up routing and notifications so each submission reaches the right reviewer or team the moment it lands.
  6. Publish by web link, email, or embed on your site or portal, then review submissions in one dashboard.
  • Client onboarding and intake: Collect background, goals, and project details before the first call, so you arrive prepared instead of starting cold.
  • HR and employee requests: Give employees one consistent way to file time off, complaints, or swag orders, with each type routed to the right reviewer.
  • IT and operations: Capture what you need to act on a change request, support ticket, or maintenance request without an email back-and-forth.
  • Healthcare and services: Gather medical history, referral details, or patient intake before the appointment so clinical staff can prepare.
  • Community and programs: Manage adoption applications, sponsorship inquiries, and daycare tour requests through a single form that routes to the right coordinator.
  • Internal approvals: Route a request through a review workflow so the right person signs off before anything proceeds.
  • Operations managers and administrators: They own the intake workflows that keep teams moving, and a structured form replaces ad-hoc email threads with one routable collection point.
  • HR managers: They handle employee-facing requests at volume, and notification routing sends each type to the right person without manual sorting.
  • Client-services teams: They need complete intake before work begins, which is why the client intake form is the most-used template in this category.
  • Healthcare administrators: They collect medical history and referral details ahead of appointments, with required fields preventing a submission that is missing what a clinician needs.
  • Small teams: They want a working form in minutes, and a tested template beats designing fields and logic from zero.
  • Keep it to 10 questions or fewer: Short forms complete at 99.0% versus 80.1% past 21 questions, so include only the fields you cannot start work without.
  • Enforce required fields: Set the fields you always need as required so incomplete submissions never reach you, and leave the nice-to-haves optional.
  • Use conditional logic to trim the form: Show a follow-up field only when an earlier answer makes it relevant, which shortens the perceived form and cuts drop-off.
  • Set routing before you publish: Decide who receives each submission upfront so requests move forward automatically, instead of routing them by hand after the fact.
  • How do I create a request form?
  • What should a client intake form include?
  • How do I automate request form notifications?
  • How many questions should a request form have?
  • What is the difference between a request form and a work order?