What to Do When an Employee Refuses to Sign a Policy Acknowledgment

It happens more than you’d expect — a new hire who wants their attorney to review the handbook first, a volunteer who pushes back on a conduct agreement, a long-tenured staff member who objects to a policy update. When it does, the organization’s response matters as much as the policy itself.

Here’s what to do, what to document, and how to protect yourself whether they sign or not.

TL;DR: An employee’s refusal to sign doesn’t mean the policy doesn’t apply to them. But without documentation of the refusal, you’re in the same vulnerable position as if you’d never sent the request at all. Document everything.

Why Refusals Are More Common Than You Think

Most refusals aren’t bad faith. They’re often confusion about what the signature means.

Employees sometimes assume that signing a policy acknowledgment means they agree with every provision — that they’re waiving rights or accepting terms they haven’t fully reviewed. In reality, a signature on an acknowledgment form means one thing: I received this document and had the opportunity to review it.

That distinction matters. Clarifying it upfront resolves most refusals before they become a problem.

Step 1: Clarify What the Signature Actually Means

If an employee hesitates or refuses, the first conversation should be clarifying, not disciplinary.

Explain that the signature is not approval of the policy — it’s a receipt. It confirms they were given the document and had the chance to ask questions. The policies in the handbook apply to them whether they sign or not.

Ask directly: “What about signing concerns you?” Most objections dissolve when the purpose is explained clearly.

Step 2: Confirm That Policies Apply Regardless

This is the point most organizations miss.

An unsigned acknowledgment does not exempt an employee from the policies it covers. Make this explicit in your conversation and in writing: the organization’s policies apply to all staff and volunteers, regardless of whether a signed acknowledgment is on file.

This matters both for enforcement and for liability. If a dispute arises later, you want a clear record that the employee was informed the policies applied to them — even if they refused to sign.

Step 3: Document the Refusal

If the employee still won’t sign after your conversation, document it immediately.

The record should show:

• The employee’s name
• The date the document was presented
• That the employee refused to sign
• Your signature and the date, as the person who presented it

If your acknowledgment form has space, add language like: “Presented to [name] on [date]. Employee declined to sign.”

If the employee also refuses to sign the refusal notation — which happens — make a separate written note, sign it yourself, and keep it in their file.

This documentation is critical. Without a signed acknowledgment or a documented refusal, you have no evidence the employee was ever informed of the policy. That gap is exactly what creates liability in disputes, audits, and legal proceedings.

Step 4: Decide Whether Signing Is a Condition of Employment

For some organizations and some policies, this is worth establishing clearly.

Employers can make signing an acknowledgment a condition of employment or continued service. If your organization takes that position, it should be stated explicitly — before a refusal happens, not after.

For harassment prevention and child safety policies in particular, the stakes are high enough that documented acknowledgment isn’t optional. If a staff member or volunteer refuses to sign those policies and you have no other method of documented acknowledgment, that’s a meaningful risk exposure — especially for churches and nonprofits managing vulnerable populations.

Consult an employment attorney if you’re considering disciplinary action or termination based on refusal to sign.

The Real Problem: Most Organizations Can’t Prove Either Outcome

Here’s what the refusal scenario actually reveals: most organizations don’t have a system that makes this easy to manage in the first place.

If you’re chasing down signatures via email, you may not even know who hasn’t signed until something goes wrong. When you do find out, there’s no easy way to document the refusal, send a follow-up, or show an auditor what happened.

A purpose-built policy acknowledgment system — like ClearPolicy — doesn’t just collect signatures. It shows you who has signed, who hasn’t, and when requests were sent and viewed. If someone refuses, you have a clear record of when the request went out, when it was opened, and that it was never completed.

When a dispute arises, that paper trail is what protects you.

What to Have in Place Before the Next Refusal

The best time to solve this problem is before it happens:

• Use a system that logs when acknowledgment requests are sent and viewed — not just when they’re signed
• Keep a clear record of every unsigned request, not just completed ones
• For high-stakes policies (child safety, harassment prevention, conduct standards), treat unsigned requests as open items requiring follow-up
• Have a documented process for handling refusals, so staff know how to respond consistently

A refusal is a compliance event. Treat it like one.