Third-party contract review requests

  • Release version: Xanadu
  • Updated August 1, 2024
  • 3 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Third-party Contract Review Requests

    ServiceNow enables employees to submit legal requests for the review of third-party contracts through a streamlined process. This functionality allows for efficient collaboration and management of contract documentation between employees and the legal team.

    Show full answer Show less

    Key Features

    • Submission of third-party documents for review.
    • Upload multiple contracts and supporting documents.
    • Feedback from internal subject matter experts.
    • Integrations with electronic signature platforms like Adobe Acrobat Sign and DocuSign.
    • Storage options for contract documents in ServiceNow or external systems (e.g., Microsoft OneDrive, Google Drive).
    • A legal contracts repository for managing signed contracts and their metadata.
    • Configurable certification of completion generation.

    Key Outcomes

    Legal fulfillers manage the review workflow, which includes creating requests, uploading, and classifying documents, and initiating internal reviews with subject matter experts. The process supports multiple iterations of feedback and revisions before finalizing documents for signatures. Once contracts are signed, they are stored in the repository for easy access by requesters and legal team members.

    Legal fulfillers can also modify requests, reclassify documents, and manage supporting materials as needed to ensure accurate documentation throughout the review process. This structured approach enhances collaboration, compliance, and contract management efficiency.

    Employees can submit legal requests for review of third-party contracts by the legal team.

    Features

    Third-party review requests include the following features:
    • Ability to submit a third-party document for review.
    • Ability to upload multiple contract and supporting documents for review.
    • Get review and feedback from the internal subject matter experts on contract documents
    • Electronic signature integrations with Adobe Acrobat Sign and Docusign.
    • Support for storing contract documents in your ServiceNow instance or external storage systems such as Microsoft OneDrive and Google Drive.
    • Legal contracts repository containing the metadata of signed contract documents.
    • Support for a configurable system property to generate a certification of completion.

    Third-party contract review request workflow

    As a legal fulfiller on the legal team, you work on assigned third-party review requests by completing the following activities:
    1. The legal user creates a third-party contract review request.
    2. The legal user uploads a single or multiple contracts and their supporting documents and classifies them.
    3. The contract fulfiller reviews the contract document attached to the legal request.
    4. If necessary, the contract fulfiller reclassifies the contract and supporting documents.
    5. If an expert review or feedback is required from internal teams, the contract fulfiller initiates internal review process.
      1. The contract fulfiller submits a review task for internal review.
        Note:
        You can create parallel review tasks for the same contract document for different reviewer groups. However, you cannot create a review task for the same document with the same reviewer group if another active task already exists.
      2. The contract reviewer is assigned the review task
      3. If the information is incomplete, the contract reviewer requests more information from the contract fulfiller.
      4. If a request for more information was submitted, the contract fulfiller shares the information.
      5. The contract reviewer reviews the document, accept, reject, or proposes edits, and adds comments.
      6. The contract reviewer reviews the contract and provides feedback. If a revised document is available, it is also shared with the contract fulfiller.
      7. The contract fulfiller receives updated document and makes the necessary changes based on the feedback.
        • For internal storage - If any changes are required, a new document version is created after finalizing the document.
        • For external storage - Reviewers collaborate on the contract document revision online in real time. Once the review is complete, the fulfiller can finalize the contract document that is available online or create a new offline version with the changes.
    6. The contract fulfiller uploads the revised contract to the contract request.
    7. The contract fulfiller emails the revised contract document to third-party contacts.
    8. View responses from third-party contacts in the activity stream of the contract request.

      Multiple iterations of revisions between your company and the third party might be necessary before the contract document is finalized by all parties. The review process may be conducted again with different reviewer groups.

    9. The contract fulfiller initiates an ad-hoc approval from the stakeholders. If the review reveals any required changes, the changes are made and a new document revision is created. The contract document can be sent for signature only when it has been approved.
    10. The contract fulfiller prepares for signatures by specifying the order in case of multiple contract documents, adding fields required in case of e-signature and sends the contract document for signature.
    11. Signatories review the contract document.
      • If no change is required, the contract document is signed by all the signatories.
      • If any changes are required, signature is declined, the user who is working on the contract request generates a new document and resends it for signature.
    12. The signed contract is stored on the ServiceNow instance or an external storage system and referenced in the contract repository. The requester and department members can access the signed contract document from the contracts repository.

    For e-signatures, after all signatories have signed the contract document, it’s stored on the ServiceNow instance or an external storage system. If an external storage is configured, the signed contract is stored in it and referenced in the contract repository.

    For wet signatures, after all signatories have signed and returned the contract document, the legal fulfiller uploads the signed contract to the contract request. The document is then stored in the contract repository.

    The requester and legal department members can access the signed contract document from the Legal Contracts repository.