# Counter-Sign a Waiver (/how-to/waivers/counter-sign-a-waiver)



When a waiver has the **Require Counter-Signature** setting turned on, customer submissions land in a pending queue and wait for an admin (or a user with the `waivers:approve` permission) to co-sign before the customer is notified. Use this guide to work through the queue.

If you're an admin and you don't see the pending queue or the "approve" action, your account is fine — you have admin bypass. If you're a non-admin user and these actions aren't visible to you, ask an admin to grant the `waivers:approve` permission.

Before you begin [#before-you-begin]

* The waiver must have **Require Counter-Signature** enabled. See the [Counter-Signatures reference](/docs/waivers/counter-signatures) for how to turn it on.
* You need admin access or the `waivers:approve` permission.
* The customer must have already submitted the waiver — your counter-sign happens *after* their signing, not in advance.

Find the pending submissions [#find-the-pending-submissions]

There are two ways to surface what's waiting on you:

1. **From the waivers list page.** In the sidebar click **Waivers**. If anyone in your company has pending counter-signatures, a banner appears at the top of the list showing the count.
2. **From a specific waiver.** Open any waiver that has **Require Counter-Signature** enabled. The **Pending Counter-Signatures** section appears at the top of the detail page above the stats cards.

Each pending row shows the signer name, matched customer, when they submitted, and two action buttons.

Counter-signing [#counter-signing]

1. On a pending row, click **Counter-sign**. A new browser tab opens in the Resytech signing app.
2. Review the customer's signed waiver shown in the embedded PDF viewer. You're seeing the same document the customer signed, with their signature visible. If your browser refuses to display PDFs inline, use the **Open in a new tab** link below the viewer.
3. Check the **printed name** field. It defaults to the first + last name on your dashboard account — edit it if you want the legal record to show a different name (for example, "Alice Smith, GM" rather than the bare account name).
4. Draw your signature in the signature pad. Touch on mobile, mouse or trackpad on desktop. Use the **Clear** button in the top-right of the pad if you want to redraw.
5. Click **Submit counter-signature**.
6. The completion screen confirms the counter-sign. You can close that tab.
7. Return to the dashboard tab. The pending row disappears automatically (the queue refreshes on tab focus). The customer is now being emailed the both-signed PDF.

If the counter-sign link fails with an "already used," "revoked," or "expired" message, see [Re-issuing a counter-sign link](#re-issuing-a-counter-sign-link) below.

Rejecting a submission [#rejecting-a-submission]

If the submission isn't acceptable — wrong signer name, blank signature, the signer didn't actually read the document, etc. — reject it instead of counter-signing.

1. On the pending row, click **Reject**. A modal appears.
2. Enter a clear, specific **Reason**. The customer reads this verbatim in an email, so write it as you would write a customer-facing note. Avoid jargon and be actionable.
3. Click **Reject Submission**.
4. The submission disappears from the pending queue. The customer receives a "Waiver Not Accepted" email with your reason. Rejection is final — if you change your mind, you'll need to ask the customer to re-sign a fresh waiver.

Re-issuing a counter-sign link [#re-issuing-a-counter-sign-link]

If your counter-sign tab is stale (link expired, you closed it and another operator already counter-signed, etc.), you can simply click **Counter-sign** again on the pending row. Each click mints a fresh 24-hour link and automatically invalidates any previous outstanding link for that submission. There's no manual revocation step.

If the submission is no longer in the queue at all, another operator either counter-signed or rejected it — nothing for you to do.

Tips [#tips]

* **The customer's confirmation email is held until you act.** If the customer is asking "did my waiver go through?", check the pending queue first. They've signed; they're just waiting on you.
* **Reason copy matters.** A vague rejection reason ("Rejected") leaves the customer confused and is bad for support volume. Specific reasons ("Please re-sign with the legal name on your booking, e.g., 'Robert Smith' rather than 'Bob'") are self-service.
* **The both-signed PDF is a separate artifact.** The customer-only PDF stays at its original location as an immutable record of customer consent. You can download either from the waiver's submissions list.
* **Two operators can't accidentally double-sign.** If two people both click Counter-sign on the same row, only one will succeed — the other receives a clean "already acted on" message.

Related How-To Guides [#related-how-to-guides]

* [Track Waiver Submissions](/how-to/waivers/track-waiver-submissions)
* [Download Signed Waivers](/how-to/waivers/download-signed-waivers)
* [Use the Waiver Editor](/how-to/waivers/use-the-waiver-editor)