PandaDoc Signature Field Not Appearing? 8 Fixes for the Most Common Cause
Your client is on the phone. They opened the proposal, scrolled to the bottom, and there’s no signature block. Or the block is there but greyed out. Or it accepts their initial but the “Finish” button stays disabled. You look at your PandaDoc dashboard, the document is definitely sent, and the recipient’s email matches. Something is wrong on the recipient side and every minute you spend hunting for it is a minute your client is deciding this is too hard.
This is the single most-reported PandaDoc issue in the wild. It has one root cause about 70% of the time, but the other 30% is a scattered mess of browser quirks, role misassignments, and locked-content traps. Below are the eight causes ranked by how often you’ll actually hit them, the exact diagnostic step for each, and the client-facing script you can send in the next 30 seconds while you fix the underlying problem.
Quick Fix Checklist
- Confirm the signature field is assigned to the recipient’s role, not to you or to “any signer” (this is the fix 7 times out of 10)
- Ask the recipient which browser they’re in. Safari and Firefox with strict tracking protection are the two most common client-side culprits
- Have them try an incognito or private window with extensions disabled, using the original email link you sent
- Verify no required field earlier in the document is blocking progression to the signature block
- Check that no conditional or locked content section is hiding the signature area from their view
- If you’re mid-call, forward them the “meanwhile” workaround in the client script section below so they can sign from a second device while you troubleshoot
Why Can’t My Recipient See the PandaDoc Signature Field?
The signature field is almost always assigned to the wrong recipient role in the template. When PandaDoc renders the document for a viewer, it only shows fields assigned to that viewer’s specific role. If your template has the signature block assigned to “Client” but the sent document’s recipient is in the “Signer” role, the field will be invisible to them.
To confirm: open the sent document in your PandaDoc dashboard, click into the recipient panel, and look at the role dropdown next to each recipient. Then open the template editor for the source template, click the signature field, and check the “Assigned to” property. The two must match exactly, character for character. Role names are case-sensitive in the field assignment.
How Do I Fix a Signature Field Assigned to the Wrong Role?
You have two paths, one fast and one permanent. Fast fix: open the sent document, click the signature field directly in the document view, and reassign it to your actual recipient using the “Assigned to” dropdown. The recipient will see the field appear on their next page refresh without needing a new email.
Permanent fix: open the source template, reassign the field at the template level, save, and then update any documents currently in flight. This prevents the same issue on every future send. If your templates were built by someone else or imported from another workspace, this misassignment is often baked in across an entire template library. It is worth a systematic audit of every template you send more than twice a month, which is where thoughtful PandaDoc template design pays back its cost within a week.
What If the Recipient Role Is Missing From the Sent Document?
The document was sent without one of the roles being assigned to an actual recipient email address. When you send a PandaDoc document, every role referenced in the template must be mapped to a real recipient. If you left the “Client Signer” role empty because you only added yourself as sender, any field assigned to that empty role becomes invisible and uncompletable by anyone.
To diagnose: open the sent document, look at the recipient list, and cross-reference against the roles used in the template. Any role with no assigned email is the culprit. The fix is to click “Add recipient” on the sent document, assign an email to the missing role, and resend. The recipient gets a fresh signing link and the field becomes visible. This is more common than you’d think for teams that share templates across sales reps, because the recipient assignment step gets skipped when someone is rushing.
Why Does the Signature Field Show But Won’t Accept Input?
This is almost always a browser issue, specifically blocked cookies or a script-blocking extension. PandaDoc’s signature capture uses JavaScript and third-party cookies for session state. Safari’s Intelligent Tracking Prevention, Firefox’s Enhanced Tracking Protection in Strict mode, and Brave’s Shields all block the exact cookies PandaDoc needs to record a signature action.
Ask the recipient what browser they’re using. Then walk them through disabling tracking protection for the pandadoc.com domain, or better, have them open the signing link in an incognito or private window with a browser that ships with permissive defaults out of the box. Chrome and Edge are the two safest recommendations.
Browser Compatibility for PandaDoc Signing
| Browser | Default behavior | Common blockers |
|---|---|---|
| Chrome (desktop) | Works out of the box | uBlock Origin, Privacy Badger extensions |
| Edge (desktop) | Works out of the box | Strict tracking prevention if enabled manually |
| Firefox (desktop) | Signature capture blocked on Strict mode | Enhanced Tracking Protection set to Strict |
| Safari (desktop) | Intermittent signature capture failures | Intelligent Tracking Prevention, Cross-site tracking prevention |
| Brave (desktop) | Signature capture blocked by default | Shields must be lowered for pandadoc.com |
| Chrome (mobile) | Works | Data saver mode can strip scripts |
| Safari (iOS) | Works if third-party cookies allowed | Cross-Site Tracking must be off in Settings > Safari |
| Samsung Internet | Works | Ad blocking extensions if installed |
The single most reliable recipient instruction: “Please open the link in Chrome or Edge in a private window.” That one line resolves about 80% of the “field is there but I can’t sign” reports.
Why Doesn’t the Signature Field Work on Mobile?
Mobile web signing works in most cases, but iOS Safari with Cross-Site Tracking enabled is the number one mobile failure point. The recipient taps the signature field, the signature pad opens, they draw their signature, and when they tap “Accept” nothing happens. The document doesn’t advance. This is Safari silently dropping the cookie that records the signature acceptance.
The fix on the recipient’s device: open Settings > Safari > Prevent Cross-Site Tracking and toggle it off, then reload the signing link. On Android, the equivalent issue appears in Firefox for Android on Strict tracking mode. Chrome for Android almost never has this problem. If your recipient is a mobile-first user and you know it in advance, include a line in your send email that says “For fastest signing, please use Chrome or the PandaDoc mobile app rather than Safari on iPhone.” It saves the call.
What Happens When the Recipient Opens a Forwarded Signing Link?
If your original recipient forwarded the PandaDoc email to a colleague, and that colleague clicked the link, PandaDoc sees a viewer whose email does not match any assigned recipient on the document. The document opens in read-only mode with no signature field visible, because signing is bound to the specific email address you addressed.
To fix: add the forwarded-to person as a new recipient on the document using their actual email address. They’ll get their own signing link. If they need to sign on behalf of the original recipient (common with executive assistants or delegated authority), you have two options. First, add them as an additional recipient with the same role, which shares signing rights. Second, edit the recipient email on the original entry to their new address, which reissues the link. Do not tell them to just click the original link again, because it will never work no matter how many times they reload.
Can Locked or Conditional Content Hide the Signature Field?
Yes, and this is one of the sneakier causes. If your template uses conditional content blocks (sections that appear only when a variable meets a rule) and the signature field lives inside one of those blocks, the signature field is invisible whenever the condition evaluates to false. Same story with locked content that requires a preceding action, like accepting a pricing table or completing a required text field earlier in the document.
Diagnose by opening the sent document in your own view, scrolling to where the signature block should be, and checking whether it’s inside a conditional section or downstream of a required field. If a required field is blocking progression, the recipient sees an error like “please complete required fields” when they try to sign, but many clients don’t read that message carefully and just report “the button doesn’t work.” Walk them page by page and confirm every yellow-highlighted required field is filled.
Why Does the Signature Field Disappear After a Page Reload?
PandaDoc uses a session token to hold the signing state. If the recipient’s session times out (usually after 30 minutes of inactivity) or if they navigate away and come back through the browser history rather than the email link, the session can partially reload with the fields hidden or greyed out. The document appears to be there but nothing is actionable.
The fix is always the same: go back to the original email, click the signing link fresh, and start over. Any progress they made on required fields will need to be redone, but the signature field will render correctly. Send this exact instruction to the recipient: “Please close the PandaDoc tab entirely, go back to the original email from us, and click the ‘Review and Sign’ button one more time.” That resets the session cleanly.
What Should I Tell My Client Right Now While I Fix This?
Send this message immediately, before you start diagnosing on your end. It gives them a working path and buys you 15 minutes to actually fix the root cause.
Thanks for flagging that. While I sort this out on my end, could you try one of these:
- Open the signing link in Chrome or Edge in a private/incognito window (Ctrl+Shift+N on Windows, Cmd+Shift+N on Mac).
- If you’re on iPhone, go to Settings > Safari and turn off “Prevent Cross-Site Tracking,” then reload the link.
- If neither works, reply to this message with a screenshot of what you’re seeing and I’ll send you a fresh link within 5 minutes.
Really appreciate your patience here.
This message works because it gives the client agency, uses their time productively while you troubleshoot, and if none of the three steps resolve it, the screenshot they send back tells you exactly which of the eight causes you’re dealing with. It is far better than “let me look into it and get back to you,” which leaves them staring at a broken document with nothing to do.
How Do I Prevent This From Happening on Future Sends?
Most of these failure modes are preventable at the template layer, not at the send layer. If you’re seeing signature field issues more than once a quarter, the fix is not tighter QA on individual sends. It is a template audit. Every field assigned to a role that actually exists, every required field flagged appropriately, no conditional content wrapping signature blocks, and a standard test-send workflow that catches misassignments before they reach a real client.
Teams that get this right during their initial PandaDoc onboarding rarely see recurring signature-field problems, because the template library is built once with the field assignments checked systematically. Teams that inherited a template library from a predecessor or from a rushed self-serve setup tend to see the same issues surface every few weeks with different clients. If that’s you, one focused afternoon of template cleanup will save your team more embarrassment than any amount of live troubleshooting.
Frequently Asked Questions
Does resending the document create a new link, or does the old link still work? Resending from the PandaDoc dashboard sends a new email with the same link. The original link remains valid unless you explicitly expire it. If you edited recipient assignments before resending, the link now reflects the updated assignments and the field will appear correctly on refresh.
Can I sign on behalf of a recipient to unblock the deal? Only if you have delegation authority documented in your contract terms, which almost no B2B relationships include. The practical workaround is to add yourself as an additional signer with the same role, complete the signature, and then have the actual recipient countersign or acknowledge separately. This is a legal grey area, so use it sparingly.
Why does the PandaDoc mobile app work when the web version doesn’t? The mobile app bypasses browser cookie restrictions entirely because it uses its own authenticated session. If a recipient reports web-signing failures, telling them to download the free PandaDoc mobile app and open the document there resolves most cookie and script issues in a single step.
Does PandaDoc support Internet Explorer or older Edge Legacy? No. PandaDoc dropped support for IE11 and Edge Legacy in 2022. Any recipient on Windows 7 or an unpatched Windows 10 machine using the old browser will see a broken interface. Instruct them to install Chrome or use a different device.
How long does a PandaDoc signing link stay valid? By default, signing links do not expire unless the document is voided, expired manually, or reaches a set expiration date configured at send time. If your document was configured with a 7-day expiration and the recipient opened it on day 8, that is the reason the field is missing. Resend to generate a new active link.
Get This Fixed Fast
If you have a client mid-signature, waiting for you to resolve this, and you’d rather hand it to someone who fixes this issue every day than lose another hour to trial and error, we can help. Our team handles PandaDoc troubleshooting and rescue help for sales teams every week, from urgent signature failures to full template rebuilds. We can be on your document within an hour and have your client signing within two.