Difficulty: Easy
Time: 60-180 minutes
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 basic NDA workflow showcases simple approval and signature routing. We’ll create an NDA that records Effective Date, Counterparty name, Initial Term Length, Governing Law, a conditional section if the counterparty is a competitor, approved by the workflow owner & a conditional legal approver if there are redlines.
The goals of this recipe are to:
Faster turnaround times for standard NDAs
Reduced legal review for low-risk agreements
Consistent, compliant contract language
Improved visibility and access to executed NDAs
Use Case
The business development team at Classics Inc. regularly engages with potential partners and clients who require NDAs before sharing any confidential information. While these NDAs are relatively standard, they still require minor customization—like adjusting the term or jurisdiction—and a basic level of legal oversight. Manually creating and reviewing each NDA slows down the team and clutters legal’s inbox.
Classics Inc. implements a simple NDA workflow in Ironclad that allows team members to generate NDAs through a guided launch form. Users input counterparty details, select from pre-approved options for terms like duration and governing law, and upload any supporting documents. If certain conditions are met (e.g., non-standard terms selected), the workflow routes the NDA to legal for quick review before automatically sending it for signature. Once executed, the NDA is archived in Ironclad’s Repository with key metadata for easy tracking.
What You'll Need
Features | Workflow Designer, Launch Form, Conditions, Approvers, Signature, Archive |
Permissions | Workflow Designer, Users and Groups edit access |
Sample Document | NDA Document (for training purposes only) |
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 a basic NDA:
Create a New Workflow
Click on Workflow Designer on the top navigation bar and create a new internal workflow.
Name your workflow “NDA Workflow”.
Click Save in the top right corner.
Upload Contract Document(s)
Select My company’s paper and upload the Sample NDA attached to this article. To access this, scroll to the bottom of the article and download the SampleNDA.pdf.
Click Save paper source.
Adjust the Lifecycle Presets, if needed
NOTE
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.
Option for Configuring the Lifecycle Presets in this workflow configuration:
Locate the question associated with the Effective Date property, then enable “Default to launch date?”
*Note: If you decide to do this, skip the step “Add question What is the effective date?” in the Configure the Create Step section below.
Delete the questions associated with the following properties from the launch form:
Termination Notice Period
Renewals Allowed
Renewal Opt Out Period
Renewal Opt Out Date
Delete the properties referenced above from the workflow configuration.
Configure the Create Step
Navigate to the Create tab and configure the launch form with the following:
Edit the Counterparty Information Section
Edit the Counterparty Information Section.
Remove the Entities question (this question is added by default).
Leave the following questions:
Counterparty Name
Counterparty Signer Name
Counterparty Signer Email
Create a New Section for Contract Information and Add Questions
Click Add section to form and title it Contract Information.
Add question What is the effective date?. *Note: Skip this step if you used the Lifecycle Preset question.
Add Competitor question.
Select Add question to section > select Yes/No field.
Add question: Is this counterparty a competitor?.
Click on Select property and map it to Competitor property.
NOTE
You may need to create a custom property for Competitor.
Add a term length question.
Select Add question to section > select Duration field.
Add question: What is the initial term of the agreement?.
Click on Select property and map it to Initial Term Length property.
Add Governing Law question:
Create a 'If the Counterparty is a Competitor' Condition for a Section
Create a new condition:
Apply Competitor condition to the document.
Navigate to the Document tab apply it to the highlighted text in the “Non-Disclosure and Confidentiality” clause.
Select the text and select Add Condition from the menu that appears, then select “Competitor = Yes”.
Tag Properties on Your Document
Select the pre-highlighted yellow text for “Effective Date” > click Add property from the menu that appears. Select Effective Date to tag property.
Repeat for the following:
Counterparty Name
Governing Law
Initial Term Length
Signature block
Counterparty Name
Counterparty Signer Signature
Counterparty Signer Name
Counterparty Signer Date Field
NOTE
The internal company signer tags will only show up if you have an internal signer added under the Sign step.Company Signer Signature
Company Signer Name
Company Signer Date Field
Configure the Review Step
Navigate to the Review tab.
Change first approver from Legal to Workflow Owner and always giving initial approval.
Change Who Can Approve to Workflow Owner.
Add Legal group as second approver.
Configure the Sign Step
Navigate to the Sign tab.
Assign Legal as the company signer.
Configure the Archive Step
Navigate to the Archive tab.
Under Record Type, select Static Record Type > select NDA from the dropdown as the Record Type.
NOTE
You may need to create a new Record Type for NDA.Set Auto-archive to Never.
Assign Legal as Archiver.
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
A Basic NDA workflow is created in Ironclad and is ready for your business users to launch. They’ll start the process by filling out a Launch Form where they’ll provide the following details:
Counterparty Name
Counterparty Signer Name
Counterparty Signer Email
Effective Date
If the counterparty is a competitor
Initial Terms
Governing Law
Conditional language will appear on the contract if the business user indicates that they are a competitor. The contract will always need to be approved the workflow owner and Legal only needs to review if there are redlines.
Tips & Variations
For low-stakes agreements, like unilateral, standard NDAs, you can streamline the process by using Public Workflows. In Ironclad, Public Workflows are used to enable self-serve contracting for standardized, low-risk agreements—like NDAs, vendor intake forms, or event agreements. They allow users across the organization (even outside the legal team) to launch workflows from a shared URL.
This low-touch approach allows business users to launch and complete contracts without legal involvement—helping your team move faster while maintaining consistency and control.
Visit the Build a Low Touch NDA Using a Public Workflow recipe to learn how to build this configuration.