---
sourceDocument: Australia Employee Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/employee-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Employee Service Management

ft:clusterId :

    - emplsm

bundleId :

    - emplsm

workflow :

    - Employee


---

# Work on a non-self-served contract review request

# Work on a non-self-served contract review request {#ariaid-title1}

Release version: Australia  
Updated June 24, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 minutes to read  
Review and revise a non-self-served contract document. As a collaborator on the request, you can email the revised document to stakeholders to verify the revisions. After they confirm the revisions, send the signature from
the contract request.

## Before you begin

Role required: sn_cm_core.contract_fulfiller

## About this task

As a collaborator added to a request, you can access and work on the request just as assignees can. However, you can't modify the Assigned to and Assignment group fields.

## Procedure

1. Navigate to your workspace.
2. On the Lists tab, navigate to Contract Requests and open a contract.

   | Option | Steps |
   | As an assignee | 1. Select the Assigned to Me option. 2. Select a request to work on. 3. If the request is newly assigned to you, select Start Work to start working on the request. The state and the Contract status of the contract request is Work in progress. {#cncore-nss-review-request__p_dgc_nfg_h1c} {#cncore-nss-review-request__ol_lt5_lb3_gtb} |
   | As a collaborator | 1. Select the Collaborations option. 2. Select a request to work on. {#cncore-nss-review-request__ol_y1q_vb3_gtb} |
   |-|-|

   {#cncore-nss-review-request__choicetable_jhj_kb3_gtb}
3. **Optional:** If you need help from other fulfillers to work on the contract request, add them in the Collaborators field.  
   Note:  
   * Users with the sn_cm_core.contract_fulfiller role are listed in the Collaborators field.
   * Same user cannot be added to the Assigned to and Collaborator fields.
   {#cncore-nss-review-request__ul_u3q_1fw_rdc}  
   The collaborators are notified via email that they have been added as collaborators to a contract request.
4. **Optional:** In the Details tab, select the Perpetual check box to specify the contract as perpetual.  
   Note:  
   The End date must be blank when this check box is selected.

   The Perpetual check box is available in contract requests that are initiated from the Sales Customer Relationship Management and Source-to-Pay Operations.
5. **Optional:** Reclassify the contract or supporting documents submitted for review.  
   Examples of reclassifying the contract or supporting documents include:
   * You can change the contract document type from a Non-disclosure Agreement to a Partnership Agreement. For more information, see [Reclassify contract documents](https://servicenow-prod.fluidtopics.net/ZTD9qZadYgUAqM2eas20DA "As a contract fulfiller, reclassify the documents submitted in a third-party contract review request. For example, you need to change the contract document type from Non-disclosure Agreement to Partnership Agreement.").
   * You can change the supporting document to a contract document. For more information, see [Reclassify supporting documents in the contract request](https://servicenow-prod.fluidtopics.net/I6UfI4MWiPxIqQacmr2osQ "As a contract fulfiller, reclassify the supporting documents submitted in the contract request. For example you can reclassify the supporting document as a contract document.").
   {#cncore-nss-review-request__ul_qvg_pmg_ldc}
6. Open an existing revision of a contract document.
   * For internal storage: Open the document revision record by navigating to the Contract documents tab and then selecting the name of the document.
   * For external storage: View the document online by navigating to the Contract documents tab and then selecting the link on the URL tab.
   {#cncore-nss-review-request__choices_t3t_lvx_czb}
7. Review the contract documents.
8. Create document revisions.  
   For more information, see [Create a document revision](https://servicenow-prod.fluidtopics.net/6U_yysAsEgHDCPo4LVd5cA "As a contract fulfiller, create a document revision to upload an updated version of the contract that contains the latest changes in the contract request, corrections, or suggestions from a third party.").
9. Analyze the contract documents to identify non-standard and missing clauses by using ServiceNow Otto for Contract Management Pro.  
   For more information, see [Contract review using ServiceNow Otto for Contract Management Pro](https://servicenow-prod.fluidtopics.net/PABUeQ0bPJ5zXbEB4SwnDg "As a contract fulfiller, you can analyze your contract documents and identify non-standard or missing clauses from the AI contextual side panel by using the ServiceNow Otto for Contract Management Pro application.").
10. If an approval is required from other stakeholders, send the document for ad-hoc approval.  
    For more information, see [Initiate an ad hoc approval for a contract document revision](https://servicenow-prod.fluidtopics.net/pyNA1eih9F0Qr7Cfi~xA7w "Initiate an ad hoc approval for a contract document revision from a user or a user group.").
11. Email stakeholders to request a review of the completed contract document and confirm the changes.  
    For more information, see [Send email to stakeholders](https://servicenow-prod.fluidtopics.net/mv6hsOOdiLV_lUVVK5sdTA "As a contract fulfiller, set up an email to stakeholders to request review of the contract document reviewed and confirm the changes.").
12. Add the internal or external signatories for the contract signatures.

    | Option | Steps |
    | Internal | 1. In the Internal Signer field, enter the name of the signer. The Authorized signatory name, Signatory, and Signatory email fields are automatically populated. 2. In the Signatory order field, enter the order in which the contract should be sent to the signer. The system starts sending the contract to the internal signer with the lowest number. Note: You can assign the same signing order to multiple signatories when you want them to sign the contract simultaneously. Signatories with the same signing order receive signature requests at the same time. 3. In the Signatory Role field, select the role for the signatory. Note: The field is enabled only for Docusign electronic signature. For wet signature and offline signature, the field is inactive and the default value is set to Signer. The Signatory Role field is visible only when the sn_cm_core.enable_docusign_signature_roles system property is set to `true`. To enable this property, see [Enable signatory roles](https://servicenow-prod.fluidtopics.net/5ReQfYV~Q3cTgg_11IE1XA "Activate a system property to display the Role field when configuring internal signatory rules and when adding signatories to a contract request."). For more information about signatory roles, see [Signatory roles](https://servicenow-prod.fluidtopics.net/iR83A81eN5IQkswsnqahvA "Signatory roles define how each participant interacts with a contract document during the signature workflow."). {#cncore-nss-review-request__ul_im4_3vk_byb} |
    | External | 1. In the Authorized signatory name field, enter the external signer's name. 2. In the Signatory field, enter the external signer's title. 3. In the Signatory email field, enter the external signer's email address. 4. In the Signatory order field, enter the order in which the contract should be sent to signers for an e-signature. The system starts sending the contract to the external signer with the lowest number. Note: You can assign the same signing order to multiple signatories when you want them to sign the contract simultaneously. Signatories with the same signing order receive signature requests at the same time. 5. In the Signatory Role field, select the role for the signatory. Note: The field is enabled only for Docusign electronic signature. For wet signature and offline signature, the field is inactive and the default value is set to Signer. The Signatory Role field is visible only when the sn_cm_core.enable_docusign_signature_roles system property is set to `true`. To enable this property, see [Enable signatory roles](https://servicenow-prod.fluidtopics.net/5ReQfYV~Q3cTgg_11IE1XA "Activate a system property to display the Role field when configuring internal signatory rules and when adding signatories to a contract request."). For more information about signatory roles, see [Signatory roles](https://servicenow-prod.fluidtopics.net/iR83A81eN5IQkswsnqahvA "Signatory roles define how each participant interacts with a contract document during the signature workflow."). {#cncore-nss-review-request__ul_j2g_jwk_byb} |
    |-|-|

    {#cncore-nss-review-request__choicetable_hm4_3vk_byb}
13. After all stakeholders agree on a contract document revision, send the contract for signature.  
    The action you take depends on the signature type.

    | Signature type | Steps |
    | Electronic signature | 1. Select Prepare for Signature. If the signatories include a gap in the signing order, the signing order is updated automatically to maintain a continuous order. The document opens on the configured e-signature portal. 2. In the e-signature portal, complete the document by adding the required fields, including the Signature field, and then select Send. {#cncore-nss-review-request__ul_plx_lfp_hjc} An e-signature envelope is created and sent to all signatories. If the system receives a success notification from the e-signature provider, the state and contract status update to Awaiting signature. |
    | Wet signature | Select Send for signature. A signature request email is sent to the first signatory. The state and contract status update to Awaiting signature. |
    | Offline signature | Select Initiate offline signature. Signature request emails are not sent to the signatories. The state and contract status update to Awaiting signature. |
    |-|-|

    {#cncore-nss-review-request__choicetable_ymt_4dx_hjc}
14. **Optional:** If you need to cancel the signature request before all signers have completed signing the document, select Cancel signature.  
    The contract request State updates to Work in Progress and the Contract document Status updates to Signature canceled.
{#cncore-nss-review-request__steps_snx_qyh_ydc}

## What to do next

* Signatories can sign or decline to sign the contract.For more information, see [Signature workflow for a contract request](https://servicenow-prod.fluidtopics.net/wLyJCDj5qisfIeC2vNAftw "Contract Management Pro supports electronic signature, wet (manual) signature, and offline signature for a contract request.").

* Check the contract request state and the contract document status in the request:
  * If all signatories sign the contract document, the contract document status updates to Contract signed. On the Signatories tab, the status of all signatories updates to Completed. You can access the contract repository record from the Contracts Repository tab.
  * If any signatory declines to sign the contract document, the contract status updates to Signing Declined. If more changes are required in the contract document, update it and resend it to the signatories for their signatures.
  * After all signatories sign the document, an email is sent to them with the finalized contract document attached.
  {#cncore-nss-review-request__ul_a2q_rh4_bwb}
* If all signatories sign the contract, you can close the request by selecting Close Complete.
{#cncore-nss-review-request__ul_vnx_qyh_ydc}