Non-disclosure agreement requests in Legal Simple Contracts
Summarize
Summary of Non-disclosure Agreement Requests in Legal Simple Contracts
Employees can submit requests to create non-disclosure agreements (NDAs) with external parties such as vendors and customers. The legal department manages these requests through a centralized system, ensuring streamlined processing and compliance.
Show less
Key Features
- Contract templates with embedded metadata and business rules for easy selection.
- Self-service functionality for creating standardized NDA contracts.
- Centralized routing of modification requests to the legal team.
- Support for electronic signatures through integrations with Adobe Acrobat Sign and DocuSign, as well as options for wet signatures.
- Document storage capabilities on ServiceNow and external platforms like Box, Google Drive, and Microsoft OneDrive.
- A legal contracts repository that maintains metadata for signed documents.
- Configurable system properties for generating completion certificates for electronically signed NDAs.
Key Outcomes
Upon submission of an NDA request, a standard contract is generated, allowing for easy customization if needed. Once finalized, the NDA can be sent for signatures and stored for future access. This process enhances efficiency, ensures legal compliance, and provides easy access to contracts for both legal teams and requesters.
Employees can submit legal requests for creating non-disclosure agreement (NDA) contracts with third parties such as vendors, customers, and partners. The legal department can manage and process these requested changes from a centralized location.
Features
- Contract templates with metadata and business rules for selecting the most relevant template for a request.
- Complete self-service for creating standardized NDA contracts.
- Requests to change the standardized contracts routed to the legal team.
- Support for electronic signatures.
- Electronic signature integrations with Adobe Acrobat Sign and Docusign.
- Support for wet signature to enable effective collaboration between the signatories.
- Document storage on the ServiceNow instance as well as external storage systems such as Box, Google Drive, and Microsoft OneDrive.
- Legal contracts repository containing the metadata of signed contract documents.
- Configurable system property to generate a certification of completion for an electronically signed non-disclosure agreement (NDA). For more information, see Activate a system property to generate a certificate of completion.
Non-disclosure agreement contract request - Workflow
When a requester submits a legal request, an NDA contract document is created using a standard contract template based on the information from the request. The information from the request is inserted at the appropriate places in the template.
If needed, requesters can request specific changes in the generated NDA contract document. The legal department can manage and process these requested changes to make necessary revisions to the NDA contract document from a centralized location.
If the generated NDA document doesn’t require any changes, the requester can send it to the signatories for an electronic or manual signature. After all signatories have signed the contract document, it’s stored in the ServiceNow instance or an external storage system. The requester and legal department members can access the signed contract document from the Legal Contracts repository.
Workflow for a non-disclosure agreement contract request
- Setting up the following items in the application:
- Multiple variations of NDA templates
- Template selection rule to choose the correct template based on the legal request
- Internal signatories for different templates
- E-signature integration - Adobe Acrobat Sign or Docusign
- Employee fills out the NDA intake request form.
- Employee previews the generated contract with metadata and sends it to the signatories.
- All signatories submit the required signatures.
- The signed contract is attached to the legal request record.
- A contract repository record is created with the metadata and signed contract.
- (Optional) The signed contract is moved to the configured storage and referenced in the contract repository section.