This Recipes program is currently in pilot, and we'd love to hear your feedback! Once you've finished this recipe, please consider taking a moment to complete this short survey to help us improve our current and future recipes.
Overview
This intake workflow allows a legal team to consolidate internal questions and requests into one channel, direct them to the right person, give transparency to requesters, and collect useful data throughout the process.
The goals of this recipe are:
- Centralized Request Management: All legal requests are tracked in one place for transparency and accountability.
- Faster Turnaround Times: Clear routing and complete information upfront reduce delays in processing.
- Improved Prioritization: Requests are automatically categorized, enabling legal teams to focus on urgent or high-value matters first.
- Better Reporting: Metadata from each request supports workload analysis and resource planning.
Use Case
At Classics Inc., employees across departments regularly submit legal requests—ranging from contract reviews to compliance questions. These requests often arrive via email, chat, or informal conversations, leading to missed details, inconsistent tracking, and delays in response times. Legal has no standardized way to prioritize or assign requests, which creates bottlenecks and reduces visibility into overall workload.
Classics Inc. implements a Legal Intake workflow in Ironclad. Employees submit requests through a guided launch form that collects all necessary details—such as request type, related documents, urgency, and business unit. The workflow automatically routes requests to the appropriate legal team member based on category and complexity, with built-in fields to capture priority and deadlines. Status updates are visible in Ironclad, keeping both requestors and legal informed without back-and-forth emails.
What You'll Need
| Features | Workflow Designer, Launch Forms, Conditions, |
| Permissions | Workflow Designer |
| Sample Contract Document | Legal Intake Workflow.docx |
Supporting Resources
Disclaimer
Ironclad is not a law firm, and this sample template does not constitute or contain legal advice. To evaluate the accuracy, sufficiency, or enforceability of specific contract terms, or the applicability of these materials to your business, you should consult with a licensed attorney. Use of, and access to, this template or any of the resources contained within the site do not create an attorney-client relationship between the user and Ironclad.
This activity is for training purposes only. The workflow you're building is a simplified example of what a Sales Order Form workflow could look like. You’re encouraged to customize it based on your organization’s unique contracting needs.
Be aware that creating properties or conditions as part of this exercise may affect your live Ironclad data. Please proceed with caution if you're working in a non-training environment.
Instructions
To build and use a legal intake workflow, follow the steps below in order:
Create a New Workflow
- Open Workflow Designer on the top navigation bar and create a new internal workflow.
- Name your workflow “Legal Intake Workflow”.
- Add this as your form description on the Create tab.
- This workflow should be used to submit any internal request or question to the legal team. After completing the launch form, you can visit the in-flight workflow to track the status of your request and communicate with the relevant legal team member.
- You can expect an initial response to your request within 2 business days. Resolutions may take longer depending on the issue.
- Click Save located in the top right corner.
Upload Contract Document(s)
- Select My company’s paper and upload this document.
- Click Save paper source.
Adjust the Lifecycle Presets, if needed
It's a best practice to use Lifecycle Presets in most, if not, all workflows. You can customize these questions, as needed, such as deleting any questions/properties that are irrelevant. You can also move the Lifecycle Preset section to the Review Step only if you don't expect your business users to know the answers, but still want this information gathered by Legal.
Best practices and common Lifecycle Preset configurations.
-
If you don't expect business users to know the information to these Lifecycle Preset questions, move the Lifecycle Preset section to Review only so that business users don’t see it in the launch form. This will still allow Legal to fill out and gather the lifecycle information.
- Move Effective Date and Term Length questions out of the Lifecycle Preset section and hide Lifecycle Preset section to Review only.
- If you delete a Lifecycle Preset question, you should also delete the property associated with that question from the workflow configuration. You'll receive a warning that the property isn't being used anywhere in the workflow.
Configure the Create Step
Navigate to the Create tab and configure the launch form with the following questions:
- Click on the “Who is the counterparty” question and click Delete question. (This question is linked to entities.)
- Move Counterparty Name out of the Counterparty Info section and to the top of the launch from. Rename the question to “What is your name?”.
- Move Counterparty Email out of the Counterparty Info section and as the next question on the launch form. Rename to “What is your email address?”
- Remove the Counterparty Info section.
- Add a drop down question and map to the “Department” property. Type in “On behalf of which department are you submitting a request?”. Add a few drop down values like “Marketing, Sales, Finance, Customer Success, Product, and Operations”.
- Add a multiple choice question and map to “Request Category” property. Label this question as “What legal area does your request fall under?”. Add the following values “Contracting/Ironclad, Data Privacy and Security, Marketing, Product, Employment, Corporate, Intellectual Property, Other.” You might have to create a new property for Request Category.
- Add a short response question and map to “Other Request Category” property. Type in “How would you describe the category for your request, if not one of the categories listed above?”.
- Add a paragraph response question and map to the “Request Description” property. Type in “Please describe your question, request, or issue. Provide as much context and information as you can to help the legal team provide an answer sooner.“ Add “If your request references a document or email thread, see instructions to attach below.” to the question description.
- Add an attachment question to the form, map it to the “Attachment” property, and label as “Please attach any relevant documents or emails needed for your request”. Fill in “If your request references an email, please use Print -> Save as PDF to turn the email into a PDF and upload the PDF and any email attachments here.” as the description.
- Add a multiple choice question and map to the “Request Urgency” property. Title this question “How urgent is this request? (How quickly does it ultimately need to be resolved)”. Add the following values:
- High (this needs to be resolved within 2 business days)
- Medium (this needs to be resolved within 5 business days)
- Low (I am awesome and have thought ahead, this needs to be resolved in 6+ business days)
- Add a short response question and map it to “Request is high urgency” property. Set the question to “Why is this high urgency?”.
- Add section to the form called “For Legal Team” and set to “Review Only”.
- Add a paragraph question to this section and map to “Request Resolution”. Label this question as “[To be filled out by legal team] Please enter the resolution or answer to the question:”.
- Add a paragraph question to this section and map to “Request Resolution”. Label this question as “[To be filled out by legal team] Please enter the resolution or answer to the question:”.
Create and Apply Two Conditions
- Request Category = Other
- If Request Category is exactly Other
- If Request Category is exactly Other
- Request = High Urgency
- If Request Urgency is exactly High
- If Request Urgency is exactly High
- Apply the “Request Category = Other” condition to the Other Request category question.
- Apply the “Request = High Urgency” condition “Why is this high urgency” question.
Configure the Review Step
- Add your first approver as “Response is in progress” with the following instructions “Legal reviewer - hit this approval to confirm you have reviewed the request and asked any initial questions of the requester”.
- Remove “Always” from “When should approval be reset?” so it says Never.
- Set your Legal group as “Who can approve” with “Rotate assignment automatically” turned on.
- Add your second approver as “Request resolved” with the following instructions “Legal reviewer - use the "Edit Info" button to enter the answer/resolution in the question in the launch form. The resolution will then appear in the legal ticket document and go into our records.”
- Remove “Always” from “When should approval be reset?” so it says Never.
- Set your Legal group as “Who can approve” with “Rotate assignment automatically” turned on.
- Under Settings turn on Turn Tracking with your internal party set as the first turn.
-
Modify your Default Email Template in Settings:
- Subject: Legal Intake Ticket for Counterparty Name
-
Body:
Hi,
Please find the Legal Intake Ticket attached. Thanks!
Best,
Emailer User Name
Configure the Sign Step
- Remove all signers.
Configure the Archive Step
- Set Record type to Static and select “Legal Intake Ticket”. If you do not see the record type, create it.
- Set Auto-archive to Always.
Test and Publish Workflow
Be mindful of properties associated with your workflow - as soon as you hit publish, any new contract properties, record types, or additional properties that you created will also automatically be pushed to the repository.
- Verify all errors and warnings have been resolved.
- Click Preview to test launch form inputs.
- Click Publish when ready.
Result
By completing this build, you’ve created a centralized, streamlined process for capturing, routing, and managing all incoming legal requests. Your workflow now:
- Guides requestors to provide all required details up front, reducing follow-up and clarifying scope.
- Automatically routes requests to the right legal team member or queue based on request type or complexity.
- Provides visibility into the status of requests for both the legal team and requestors, reducing ad hoc status check-ins.
- Generates valuable metadata for tracking request volume, turnaround times, and resource allocation.
With this foundation in place, your legal team can manage its workload more efficiently, improve responsiveness, and create a consistent intake experience for the business.
Tips & Variations
- Refine your launch form questions over time by reviewing recurring incomplete or unclear submissions.
- Integrate with Slack to notify assignees immediately when a new request is submitted. Visit the Slack Integration course to learn more about this feature.