Request Form Examples (Workflow)

Modified on Tue, 17 Dec at 2:06 PM

Request forms play a crucial role in facilitating effective communication and collaboration between stakeholders and creative teams. Proper creative briefing leads to better collaboration, increased alignment, and higher stakeholder satisfaction. When you invest in a great Request Form, you'll see the results later in your workflow with metrics like reduced time to first proof, reduced number of proof versions, and faster turnaround on Projects.


In this article, we will explore different types of creative Request Forms, empowering you to choose the right form for your unique requirements.


Features described in this article are not included in all subscription plans. 
Interested in expanding your feature set? Please reach out to success[at]lytho[dot]com. Have a question about your current subscription? Contact our Support Team for further assistance.


TABLE OF CONTENTS



Request Form Creation Checklist

Before you begin, answer these: 

  • What type of content is this for? 
  • What do I want this form to achieve? 
  • Are there any bottlenecks or known process gaps I want to solve? 
  • What information does my team need to complete the request and operate efficiently?


While you are building, check these:

  • Identify who is responsible for accepting Requests. Include the Acceptors field and add the person(s) responsible for accepting Requests. Without an Acceptor, no notifications will be sent when the form is submitted!
     
  • Include questions that will give your team enough direction to do their work. This can’t be achieved with a single field, but it’s important to consider throughout the building process. Be sure to ask for any details that should be included, and provide ample opportunity for your requesters to share their ideas to reduce feedback cycles once the work is ready for review.
     
  • Identify the questions that are essential to completing the Request. Each field has the option to be required for form submission, indicated with an asterisk to the requester. When editing a field, select the checkbox next to Required.
     
  • Include instructions that will help Requesters understand how to complete the form. Using the Static Text field gives you the ability to provide instructions or headers for clear communication. Utilize Helper Text in Text, Longform Text, and Number fields to provide examples of the information you need or further instruction.
     
  • Identify any resources Requesters should reference, such as previously created content or company brand guidelines. Provide these with the Link field.
     
  • Consider how long your team needs to complete the Request and if there are any constraints on lead times or service level agreements (SLA’s). Enforce this in your Due Date and Date fields by limiting the dates available for selection.
     
  • Determine if there is a Project Template that should be mapped to the associated Work. Define this in the Project Template field to select the template by default. Acceptors will still be able to select from other available templates for flexibility.
     
  • Identify any tags that should be mapped to the associated Work for categorization and reporting. Define these with the Tags fields.
     
  • Determine data points that are important for your team to map to Projects for visibility and reporting needs. Use your Custom Fields* to track these important data points directly from the Request Form. 
Download the interactive checklist HERE.



General Request Form 

A general creative Request Form serves as a comprehensive tool to capture various types of creative Requests. It typically includes fields for the Project name, description, objectives, target audience, desired format, and any specific branding guidelines or assets.


This type of form can be used when strategic advice from the creative team is needed, and the Requester might not know which type of deliverable they are requesting.



Guide your Requesters to provide the information you need by providing Helper Text.



Request Forms for Specific Deliverables

Individual Request Forms can be created for each type of deliverable. These forms do not contain conditional logic and can be built using the form template builder.


It is assumed that the Requester knows what type of deliverable they need for their project.


HTML Email Example Form



Social Media Example Form



Video Example Form



Web Banner Example Form



Postcard Example Form



Concierge Form with Conditional Logic

Conditional Logic allows you to hide or show fields or sections of the form based on a value selected. For example: if a checkbox field "Postcard" is checked, then the "Postcard" section of the form, containing relative fields, is displayed.


This means that one form can be used to give users the ability to choose which deliverable they would like to request.


Forms built with the Form Template Builder and forms built by our Support Team both provide powerful functionality. Find a comparison here.


Forms with conditional logic need to be updated by our Support Team. Request changes to the forms here.









Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article