---
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


---

# Signature workflow for a request

# Signature workflow for a request {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 8 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 Signature workflow for a request

Contract Management Pro for Legal Service Delivery supports three signature types for contract requests: electronic signature, wet (manual) signature, and offline signature.
This workflow enables ServiceNow customers to send contracts to signatories, track signing progress, and manage signed documents efficiently within the platform.
Show full answer Show less  

## Electronic Signature Workflow

* The finalized contract is sent to signatories in a predefined order via electronic signature providers such as DocuSign or Adobe Acrobat Sign.
* Signatories receive email notifications with links to sign the document electronically; multiple signatories can sign simultaneously if assigned the same signing order (except in Employee Center).
* Signatories can sign or decline the contract; status updates reflect each action, and a certificate of completion can be generated if enabled.
* If one or more signatories opt for wet signatures, the workflow supports uploading the manually signed PDF and continuing electronic signatures for remaining signatories, resulting in a Mixed signature type.
* Failure to deliver signature requests triggers notifications and options to update signatory information or upload manual signatures.
* Contract users and fulfillers can submit changes and resend updated documents for signature as needed.
* Signatory roles can be enabled to control participation in the workflow based on assigned roles.

## Wet Signature Workflow

* The contract is sent as PDF attachments for manual signing; signatories receive email notifications with the document.
* Signatories print, sign, and return the document to the contract fulfiller, who uploads the signed version and sends it to remaining signatories.
* Only signatories with the Signer role participate; others like Viewer or Approver are excluded.
* After all signatures are collected and uploaded, the contract is added to the repository and the request status updates accordingly.

## Offline Signature Workflow

* Used when contracts are signed outside Contract Management Pro (e.g., in-person or third-party apps).
* The contract request is set to Offline signature type; no signature request emails are sent.
* The fulfiller uploads the signed document to record completion, and statuses update to Contract signed.

## Managing Signature Workflows

* Changing from electronic to wet signature removes non-signer roles and enforces sequential signing.
* Modify signatories feature allows adding, removing, editing, or reordering pending signatories while pausing the workflow temporarily.
* Resume signature resumes the workflow; if not resumed within a configured time, changes revert automatically.
* Resend signature request enables manual triggering of signature emails if needed.
* Wet signature processes for NDA legal requests can be canceled by legal users.

## Contract Document Access and Validation

* Contract fulfillers can view and update documents; only contract administrators can delete documents.
* Requesters and users on the watch list have restricted viewing rights based on their association with the contract request.
* During repository record generation, mapped fields are validated; errors trigger email notifications with corrective instructions.

## Practical Actions for ServiceNow Customers

* Upload manually signed contract documents for wet or mixed signature workflows.
* Initiate offline signature workflows to record external contract signings.
* Modify signatories mid-process to adapt to changes without restarting workflows.
* Cancel wet signature workflows for specific contract types when necessary.

This signature workflow streamlines contract approval and execution, ensuring visibility, control, and compliance in contract management processes within ServiceNow.  
Contract Management Pro for Legal Service Delivery supports electronic signature, wet (manual) signature, and offline signature for a contract request.  
* Electronic Signature: Enables signatories to sign the contract document electronically. For more information, see [Configure an e-signature provider](https://servicenow-prod.fluidtopics.net/OhZIXxRFIL6uoz~pzjIERA "Configure an electronic signature provider to enable users to sign contract documents electronically.").

  To generate a certificate of completion, select the Electronic Signature as the signature type in the contract request. For more information, see [Activate a system property to generate a certificate of completion](https://servicenow-prod.fluidtopics.net/oxooq9a27c2t7EdTsRQnYA "As a contract configurator, activate a system property to generate a certificate of completion for electronically signed contracts.").
* Wet Signature: Enables signatories to sign the contract document manually. You can then upload the signed document to a contract request. For more information, see [Upload a signed contract document](https://servicenow-prod.fluidtopics.net/E9k9jwvHJL1Ie8J5D6bxgw "Upload a signed contract document that you have received from the signatories. You must upload a contract document for a wet signature workflow, an offline signature workflow when the contract was signed outside the system or if one of the signatories in the electronic signature workflow decides to do a wet signature.").
* Offline signature: Records a contract that has been signed outside Contract Management Pro. Signature request emails are not sent to the signatories. The fulfiller or contract user uploads the signed document directly.
{#snlc-lsd-signature-workflow__ul_wmz_1rn_hxb}

## Electronic signature workflow {#snlc-lsd-signature-workflow__section_etk_fqb_gyb}

* Send the finalized document to the signatories for signing.
  * The state and contract status updates to Awaiting Signature and the electronic signature flow is triggered as configured in [Configure an e-signature provider for legal contracts](https://servicenow-prod.fluidtopics.net/Ntu68XNiyNsOs0CaSEXRSg "Configure an electronic signature provider to enable users to sign contract documents electronically.").
  * An email notification that the contract document is available for signature is sent to the first signatory. The email contains a link to the contract document that the signatory can open and sign the document through the Docusign or Adobe Acrobat Sign electronic signature provider.

    Signatories receive signature request emails according to the order set in the Signatories tab.  
    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 and can complete their signatures independently.  
    Note:  
    This option is not available when you set the signing order in Employee Center.
  * The signatory fields---such as Name, Title, and Email---are not pre-filled in the contract document before it is sent for signature. The electronic signature provider populates these fields when the signatory accesses the document to sign it.
  {#snlc-lsd-signature-workflow__ul_i1s_rrb_gyb}
* Signatories can sign or decline the contract document.{#snlc-lsd-signature-workflow__table_t4x_51l_s2c__entry__2}

  | Signatories action | Workflow |
  |-|-|
  | All the signatories choose to do an electronic signature | * First signatory signs the contract documentIf there is more than one signatory, the contract document is sent to the next signatory in the order. The status of the current signatory in the request updates from Pending Signature to Signed. The status of the next signatory updates from Not Started to Pending Signature. * After the last signatory signs the document, the contract repository record is created and the signed document is attached to it.For contract requests containing multiple contract documents, the signed contract document is split into individual documents and attached to the contract repository record for the respective contract type. The state of the requests updates to Contract Signed. {#snlc-lsd-signature-workflow__ul_lsz_5hs_52c} |
  | One or more signatories decide to do a wet signature | * One or more signatories decided to do a wet signature instead of electronic signature. * The wet signed contract document in PDF format is shared with the contract fulfiller. * The contract fulfiller uploads the signed document, selects the signatories who have shared the wet signed contract document and proceeds with the signature workflow by sending the document to the next signatories.The status of the signatory in the request updates from Pending Signature to Signed. The status of the next signatory updates from Not Started to Pending Signature. The signature type is updated to Mixed signature after all the signatories have signed the document. * After the last signatory signs the document, the contract repository record is automatically created and the signed document is attached to it.For contract requests containing multiple contract documents, the signed contract document is split into individual documents and attached to the contract repository record for the respective contract type. The state of the requests updates to Contract Signed. {#snlc-lsd-signature-workflow__ul_p2t_jql_s2c} |
  | The document is declined by the signatory. | An email notification is sent to the requester when a signatory declines to sign the document. The Signatory status in the request updates to Declined. The State changes to Work in progress and the Contract status changes to Signing Declined. |
  |   |   |
  | The signature request is not delivered to a signatory. | The Signatory status in the contract request changes to Delivery failed. The state of the contract request changes to Signature delivery failed. An email notification is sent to the contract fulfiller informing them that the signature request could not be delivered. A notification appears on the contract request informing about the undelivered signature request and the available actions for the fulfiller. * For Docusign, you can update the signatory's information and retry, cancel the signature process to restart it, or upload a manually signed contract. * For Adobe Acrobat Sign, you can cancel the signature process to restart it, or upload a manually signed contract. {#snlc-lsd-signature-workflow__ul_wjq_j2l_33c} |
  | The contract document is resent for signature. | For contract request fulfilled by the contract user: A contract user can submit a change request. The contract fulfiller works on the change request and sends the updated document back to the contract requester. The updated contract document is sent for signature by the contract user. For contract request fulfilled by contract fulfiller: The contract fulfiller creates a document revision manually or by using regenerate option and resends the document for signature. |
  [Table 1. Signatories action on the contract document]

  {#snlc-lsd-signature-workflow__table_t4x_51l_s2c}  
  Note:  
  When signatory roles are enabled, each signatory participates in the electronic signature workflow according to their assigned role. For information about available roles and how to enable them, see [Signatory roles](https://servicenow-prod.fluidtopics.net/iR83A81eN5IQkswsnqahvA "Signatory roles define how each participant interacts with a contract document during the signature workflow.").

  If the system property sn_cm_core.enable_executed_contract_audit_certificate is set to true, the certificate of completion is generated and
  attached to the contract repository record.
{#snlc-lsd-signature-workflow__ul_v1c_15b_gyb}

## Wet signature workflow {#snlc-lsd-signature-workflow__section_cgv_ftb_gyb}

* Send the finalized document to the signatories for signing.
  * The state and contract status are updated to Awaiting signature.
  * An email notification is sent to the first signatory in order and the contract documents are attached as PDFs in the email.The current signatory is placed in the To field of the email. The following recipients are placed in the CC field:

    * Contract fulfiller
    * Person who opened the contract
    * Person for whom the contract was requested
    * Initiator of the send for signature action
  {#snlc-lsd-signature-workflow__ul_dgv_ftb_gyb}
* Signatories accept or decline the document.{#snlc-lsd-signature-workflow__table_bhy_sqw_cfc__entry__2}

  | Signatories action | Workflow |
  |-|-|
  | The current signatory accepts the document and there are pending signatories | * The signatory prints the contract document, signs it, and then returns it to the signature requester. * After receiving the signed contract document, the contract fulfiller uploads the signed contract and sends the document to the pending signatories. {#snlc-lsd-signature-workflow__ul_vlk_vsk_dfc} |
  | The signatory declines the document | The signatory sends the document back to the requester for corrections. The signatories and the contract fulfiller can collaborate and finalize the contract document. |
  | All the signatories have signed the document | * After receiving the contract document signed by all signatories, the contract fulfiller uploads the signed contract document in PDF format. * The contract document is added to the repository after it is uploaded. {#snlc-lsd-signature-workflow__ul_ekh_2ly_dfc} For self-served contracts, the state of the request updates to Closed complete and the contract status updates to Contract signed. For non-self-served contracts, the state of the request and the contract status updates to Contract signed. To close the contract request, select Close complete. For more information, see [Upload a manually signed contract document](https://servicenow-prod.fluidtopics.net/nwH72FolaL4Rkhc8XLtypA "Upload the wet signed contract document you have received from the signatories. You need to upload a contract document for a wet signature workflow or if one of the signatories in the electronic workflow decides to do a wet signature."). |
  [Table 2. Signatories action on the contract document]

  {#snlc-lsd-signature-workflow__table_bhy_sqw_cfc}

{#snlc-lsd-signature-workflow__ul_unr_q1q_pbc}  
Note:  
In the wet signature workflow, only signatories with the Signer role participate. Signatories with Viewer, Receiver, or Approver roles are not included. For more information, see [Signatory roles](https://servicenow-prod.fluidtopics.net/iR83A81eN5IQkswsnqahvA "Signatory roles define how each participant interacts with a contract document during the signature workflow.").

## Offline signature workflow {#snlc-lsd-signature-workflow__section_offline_workflow}

Use the offline signature workflow when the contract is signed outside Contract Management Pro. For example, the parties sign the contract document in person or through a third-party application, and you want to record the signed document against the contract request.

* Set up a contract request for offline signature.
  * Create a contract request with Offline signature selected as the signature type.
  * On an existing contract request, change the signature type from Electronic signature or Wet signature to Offline signature.
  {#snlc-lsd-signature-workflow__ul_offline_initiate}
* The fulfiller or contract user selects Initiate offline signature.
* The state and contract status update to Awaiting signature. Signature request emails are not sent to the signatories.
* The signatories sign the contract document outside Contract Management Pro.
* The contract fulfiller uploads the signed document.
* The state and contract status update to Contract signed. The status of all signatories updates from Not started to Completed.
{#snlc-lsd-signature-workflow__ul_offline_workflow}

## Changing the signature type from e-signature to wet signature {#snlc-lsd-signature-workflow__section_signing_method_change}

Wet signature supports only Signer role and sequential signing. If you change the signature type from electronic signature to wet signature:

* Signatories with Viewer, Receiver, or Approver roles are removed.
* Signatories with the same signing order are assigned sequential signing order, and any gaps in the signing order are removed.
{#snlc-lsd-signature-workflow__ul_signature_type_change}A message notifies you of these changes so that you can review the Signatories tab before continuing with the signature workflow.

## Modify signatories when the signature workflow is in progress {#snlc-lsd-signature-workflow__section_q2g_5z5_5fc}

Modify signatories enables you to add, remove, edit, or reorder pending signatories while a signature workflow is in progress. Initiating this action pauses the signature workflow for a duration defined
by the system property maximum_signature_pause_duration. To continue the signature workflow after making changes, use the Resume Signature option to resume the workflow.  
The workflow can progress as follows:

* Use Modify signatories option to modify the signatories.
* Add, remove, modify, or reorder signatories.  
  Note:  
  * For signature block-based contract templates, you can add, modify, remove, and reorder actions, whereas for participant based templates, only modify and reorder actions are enabled.
  * Modify signatories option is available in wet signature workflow and Electronic signature workflow with Docusign electronic signature provider integration.
  {#snlc-lsd-signature-workflow__ul_uby_wkr_1gc}
* Select Resume signature to resume the signature workflow once modifications are complete.  
  Note:  
  If the signature workflow is not resumed within the configured time duration, any changes made to the signatories are reverted, and the signature workflow resumes from its previous state.
* Signature request email notifications are sent to the signatories.
* After the last signatory has signed the document, the contract repository record is created and the signed document is attached to it.

{#snlc-lsd-signature-workflow__ul_zrz_zyk_vfc}For more information, see [Modify signatories](https://servicenow-prod.fluidtopics.net/lwaCXX1NhGKSk5inR9WBIQ "Pause an active signature workflow to add, modify, reorder, or remove signatories on a contract request that is in Awaiting signature state.") and [Resend signature request](https://servicenow-prod.fluidtopics.net/~Vz1U~uimw1dJVJOUq7LlQ "Resend signature request functionality enables contract fulfillers to manually trigger signature request when needed.").

## Contract document access {#snlc-lsd-signature-workflow__id_ybf_wcr_pbc}

Access to a contract document is based on the following user roles and conditions:

* A contract fulfiller can view and update contract documents
* Only a contract administrator can delete contract documents.
* Requesters can view only the contract documents for which they submitted the contract request.
* Users added to the watch list can view only contract documents for contract requests they have added.
{#snlc-lsd-signature-workflow__ul_n1z_qzy_5qb}

While generating the contract repository record, mapped fields and their values are validated for data type and correctness. If validation errors are found, an email notification is sent to the contract fulfiller. The email
also displays the list of fields that were not copied into the final contract document and the link to the contract repository record. The fulfiller then opens the record using the link and corrects the values to resolve the
validation errors.
* **[Upload a manually signed contract document](https://servicenow-prod.fluidtopics.net/nwH72FolaL4Rkhc8XLtypA)**   
  Upload the wet signed contract document you have received from the signatories. You need to upload a contract document for a wet signature workflow or if one of the signatories in the electronic workflow decides to do a wet signature.
* **[Initiate an offline signature for a contract request](https://servicenow-prod.fluidtopics.net/G3hIYKezzGuoH~gZGfRVVQ)**   
  Initiate an offline signature when a contract is signed outside Contract Management Pro and record the signed document in Contract Management Pro.
* **[Modify signatories](https://servicenow-prod.fluidtopics.net/lwaCXX1NhGKSk5inR9WBIQ)**   
  Pause an active signature workflow to add, modify, reorder, or remove signatories on a contract request that is in Awaiting signature state.
* **[Resend signature request](https://servicenow-prod.fluidtopics.net/~Vz1U~uimw1dJVJOUq7LlQ)**   
  Resend signature request functionality enables contract fulfillers to manually trigger signature request when needed.
* **[Cancel a wet signature process for non-disclosure agreement legal requests](https://servicenow-prod.fluidtopics.net/T3kbDkJa0jb7xdKHnL2skA)**   
  As a legal user, cancel the wet signature process for contract documents in NDA legal requests that have been sent to signatories.

**Related concepts**   

* [Non-disclosure agreement requests](https://servicenow-prod.fluidtopics.net/8nt95wiIX4hNwatrKhLxQw "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.")
* [Third-party contract review requests](https://servicenow-prod.fluidtopics.net/Mzwabst5~JOj_gFNWVhXQA "Employees can submit legal requests for review of third-party contracts by the legal team.")
* [Contract amendments](https://servicenow-prod.fluidtopics.net/LlkDfz1Caftg6s9HtL9lcg "The contract amendment workflow enhances contract lifecycle management by enabling you to initiate, track, and finalize amendments to existing contracts with an audit trail.")
* [Linking parent-child contracts](https://servicenow-prod.fluidtopics.net/~SlpAl2RBvPV8y8B690NGg "Link a parent contract to a child contract to establish hierarchical relationships between contract requests and inherit fields from the parent contract request.")
* [Internal review overview](https://servicenow-prod.fluidtopics.net/Ox0VKmvtxg2awWgYH~EbuQ "Get your content reviewed by internal teams who have the expertise you need.")
* [View and download a signed contract document](https://servicenow-prod.fluidtopics.net/J~neK4DFRW82me9o37arzw "View and download a signed contract document.")
* [Manage Contract Management Pro for Legal Service Delivery](https://servicenow-prod.fluidtopics.net/i4SbSyuxkyYd8hBHhyUHKg "As administrator work on managing the word document templates and legal contracts.")  
**Related tasks**   

* [Cancel a legal request](https://servicenow-prod.fluidtopics.net/VU0Vgim6HRIE5W8~XmopLw "Cancel a legal contract request if it is no longer necessary.")
* [View contract requests](https://servicenow-prod.fluidtopics.net/sRh_sFP_YTaq6Faav8BP0Q "When a legal request is submitted a contract request associated with it is initiated.")