Correcting a Document Sent for Signing

Keep the original request, correction and outcome connected

Published

Navy-and-orange illustration follows inspection of an incorrect signing document, a decision connecting earlier and revised requests, and verification of retained results.

A supplier agreement goes out for signing with an older equipment schedule attached. Procurement spots the mistake after a recipient has opened the request. The approved schedule is already in the contract file, but sending a second request leaves two requests in circulation and an unclear record of what happened.

Check the live signing status, take the authorised correction or cancellation action, and preserve the connection to the original request. Record what was sent, what recipients did, why the change was needed and which result the contract owner accepted. A corrected source document alone does not resolve a request already with the signing provider.

Inspect the request before choosing a remedy

A signing request has content, recipients, routing and a current provider state. In DocuSign, the envelope groups those details. Identify the affected agreement and envelope, exact documents, recipient configuration and the error. Use current provider information when deciding the next action, because a recipient may act while staff investigate.

DocuSign's correction guidance limits its correction view to envelopes in sent or delivered states and requires the relevant account permission. Completed, voided and declined envelopes cannot use that correction route. The same guidance limits voiding to sent or delivered states. The permitted action therefore depends on current status, account settings and the proposed change, as well as the organisation's approval rules.

Illustrative review decisions for a sent signing request; confirm the provider's supported action.
Issue foundDecision to makeHistory to preserve
Contact detail needs correctionVerify the intended recipient and authority, then check whether a provider-supported correction is permitted.Earlier and corrected details, reason, approver, timing and provider outcome.
Wrong document or terms were selectedReview the affected content and choose an authorised correction or void the active request before issuing a replacement.Sent versions, applicable approval, change decision and corrected or replacement request.
A recipient has already actedInspect the actual activity and current envelope state; obtain the business or legal review needed for those facts.Available recipient activity, any signature evidence, affected content and the agreed response.
The envelope has completedRoute the issue for an authorised amendment, replacement agreement or other resolution.Completed result and evidence, the error assessment and the separate corrective decision.

Avoid treating every wrong attachment as the same case. The organisation may choose a replacement for clarity even where a provider permits some editing. A typo in a verified contact detail and a changed price can require different approvals. Record the decision that applies to the actual request.

Preserve the earlier request and verify the action

  1. 1 · Inspect

    Identify what happened

    Connect the sent documents, provider request, current status and available recipient activity.

  2. 2 · Decide

    Authorise the response

    Choose the permitted provider action and the content, recipients and approvals for any further request.

  3. 3 · Verify

    Accept the resolved result

    Confirm the earlier outcome and retain the corrected or replacement documents with the contract history.

Keep the sent document versions and approval reference distinguishable from later edits. If the same envelope is corrected, retain the changed details and activity around that correction. If a new envelope is issued, link both requests and the reason. The provider's transaction identity and the document's version identity answer different questions.

A requested cancellation is not a confirmed void. Verify the provider result before marking the earlier request resolved. If the action fails or the state changes, assign the exception and reassess the current facts. A local status label or message asking recipients to ignore the request cannot substitute for the provider action.

Worked example: the older equipment schedule

This fictional correction extends AGR-1042. Commercial review approved the agreement with equipment schedule revision 3, but the sender attached revision 2. One recipient has viewed the request and neither has signed when the error is confirmed. The organisation's procedure calls for voiding this active request and issuing the checked package again.

  1. Identify the exact mismatch

    Procurement connects the provider envelope to the documents actually sent and the approval for revision 3. It records the error and checks current status and available recipient activity. The approved source and the incorrectly dispatched pack remain distinguishable.

  2. Confirm the earlier request's outcome

    An authorised operator requests the provider void with the correction reason. Staff verify the returned status and retain the relevant outcome. If the envelope completes first or the void is rejected, the owner follows a different review path instead of recording a successful cancellation.

  3. Check the package and approval for reissue

    The owner confirms the agreement, revision-3 schedule, intended recipients and routing against the existing approval. Any changed terms return for the required review. The release check records who authorised sending this exact set.

  4. Link and explain the replacement

    The new envelope remains connected to AGR-1042 and the earlier voided request. The communication identifies the replacement clearly. Staff retain the issued message and available delivery or failure evidence; they do not assume that everyone read it.

  5. Accept the replacement result

    After completion, the owner checks the expected signed documents and provider evidence and retains them with both request histories. The workflow then applies its agreed effective-date and activation rules. A delayed event referring to the earlier request is reconciled against that request, not accepted as the replacement's result.

Preserve the completed record and its evidence

An error found after completion needs a resolution tied to the completed record. Preserve the returned documents and available execution evidence. The authorised business and legal owners determine whether the response is an amendment, a new agreement or another action. A provider status does not decide the legal effect of the agreement.

FormKiQ can retrieve the associated envelope's provider-recorded activity. Viewing that history does not automatically preserve a permanent evidence snapshot, prove inbox delivery or validate a cryptographic signature. Configure the required activity and signed-output storage as part of the workflow, with access and retention appropriate to the contract file.

The correction record may contain personal contact details or confidential terms. Keep access aligned to departments, contract responsibilities and any customer-tenant boundaries. Include the documents and recipient information sent to DocuSign in the provider-processing review. Voiding a request does not recall a copy already downloaded.

The contract management and eSignature guide covers the wider approval-to-signing handoff. The post-signature guide covers the continuing agreement file, and the PDF signature guide explains the separate validation question.

Review one signing correction

  • Resolve the agreement, actual sent versions, provider request and current status.
  • Confirm the error, affected recipient activity and authority for the chosen response.
  • Verify the provider's correction or void outcome, including a changed or rejected state.
  • Retain the original details and link the corrected or replacement request to its approval.
  • Check the expected returned documents and evidence before accepting the resolved result.
  • Preserve completed records and route legal effect, confidentiality and further action to the responsible owners.

Make the correction part of the agreement's history

A signing correction should explain the earlier request and the decision that resolved it. Use the current provider facts, authorise the appropriate response and verify the result before continuing the business workflow. Keep the original request connected so the accepted contract record remains understandable.

      Start with FormKiQ Core

      The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.

      Get Started Free

      Deploy FormKiQ Essentials or Advanced

      Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.

      Explore Options

      Plan an Enterprise Rollout

      For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.

      Book a Call