Workaround for Draft Request Forms

While I haven’t thoroughly tested this, custom item types could be used to set up the ability to create draft form requests. I've outlined the steps for setting up and using this method below. Depending on your needs, there may be some downsides which I’ve noted in the pros and cons list at the end of this post.

Part A: How to Setup the Ability to Create Draft Requests

1. Create a folder for draft requests with the same custom fields as the live folder where form submissions are typically received. (Or, if there are certain fields that should be filled out by the team who receives the request like assignee, those fields would be excluded from the draft folder.) Share full access with any user who needs the ability to create a draft request. 
   
   
2. Create a custom item type with the following setup:

• Available in the quick access menu
• Default workflow is the same as the folder in which the live request will end up
• Default description includes all questions that would typically be answered via the form.
  (The level of effort on this can be minimized by taking an existing request form entry, converting it to a blueprint, and deleting the content that was submitted through the form, so you’re only left with the form sections and questions.)

Part B: How to Create Draft Requests

1. When a user needs to start working on a draft request, they will go to the folder created in Part A - Step 1 and add the custom item created in Part A - Step 2.
   
   
2. (Optional) User shares the item with any other collaborators who will help fill out the necessary info.
   
   
3. Once the necessary info and custom fields are complete and the request is ready to submit, the user moves the item to the appropriate parent folder.
   
   
4. Once the request is added to the new parent folder, the receiving team can fill out any additional fields, add subtasks from blueprints, and trigger automations as needed.

✅ Pros:

• Form info can be saved as a draft
• Allows you to tag in teammates for collaboration in filling out the form template
• Many types of automations can still be used (e.g., when custom field changes to xyz > add subtask from blueprint; when a new item is created in folder abc and custom field contains xyz > assign to person A; etc.)

❌ Cons:

• Requires full user license, cannot be done with only a contributor license.
• Requires users to have some level of access to the folder in which form requests are received.
• Users may have visibility into other draft requests being worked on in the drafts folder. If too much transparency is a concern, that could be mitigated by creating separate draft folders for individual teams.
• Can’t use form logic for conditional questions so multiple form templates may be needed for each variation.
• Potentially requires more user training or detailed SOP instructions for things like proper status selection and parameters for triggering automations.