How to decline or void a signature request without leaving a ghost

When the sum, the scope or the date is wrong. When you lack authority. When you have not read and will not pretend. The button exists for a reason. Use it with one honest sentence: 'clause 4 is not what we said on the call'.

Do not decline because you are lazy and hope they forget. Then you get a nudge, then a call, then a sour mood. Say no, or say 'next week' outside the tool and ask for a new deadline.

BankID is irrelevant here. You are refusing a yes, not an identity level. An SES no is a no.

A reason in the decline button is evidence. A no with no reason is still a no, but worse in an email thread three months later.

Sign and 'sort it after'. Then you said yes. After is an add-on or a fight.

Forward the link to a colleague who 'will handle it'. Links may be personal. You mess up who actually saw the document.

Print, cross out, scan, send as a new attachment. Then you left the flow. The sender sits with an open job and a shadow file.

Do not void to hide that you sent too early. Say you sent too early. Trust can stand that. Hiding cannot.

Wrong file. Wrong person. The deal died in negotiation. Then you drop it. Status should become 'voided', not 'maybe'. The team learns from what they see in the list.

Tell the people who already got the email. A short note: 'pulled, new one coming' or 'we're dropping this'. Links that live with no explanation are how people distrust the next send.

If someone already tagged, their yes is tied to an unfinished flow. Do not reuse that file as 'almost signed'. New job, new marks.

If the other side declines and you agree the text was nonsense, say thanks. That is cheaper than a yes they regret in production.

Set expiry. A job with no end is a ghost. When it expires, archive it as expired, not as personal failure by the other side — unless you have called.

A reminder is not a void. Three nudges without dropping is nagging. Nagging kills relationships and trains people to ignore the next NDA too.

In a small team with no IT: someone must own the list. Friday, five minutes, kill dead jobs. That is hygiene, like dishes.

In a fight, 'they never got it' meets 'yes they did, 12 May, they opened it'. A timed decline cuts that. Holes in the log feed stories.

The evidence pack should survive a no. If the tool deletes everything on void, you have a worse trail. Check that before you need it.

PAdES on a finished file does not exist if the flow never finished. Do not pretend a half envelope is a signed contract.

Fix the text. Send again. Mention that the last one was voided. People can stand that. They cannot stand being asked to sign 'the same thing' when it was not the same thing.

If the relationship is broken, stop. A tool is not therapy.

Honest SES tools treat decline and void as first-class acts, not shame corners. Use them like clearing a table, not like losing.

A holiday cover who gets the link and tags in a panic: void, explain, send to the right human. SES cares that someone said yes, not whether they should have. The role should have been clear.

The wrong company name in the PDF is not only a decline-versus-void question in law. It is 'this is the wrong document'. Drop, fix, new flow. Do not ask them to 'ignore line 1'.

Double send: two jobs, two logs. Void one immediately. Otherwise you have two yeses on almost-the-same files and a future fight about which one counted.

Make a team sentence: we void within five working days of no life after a nudge and a call. Without that sentence, ghosts live because nobody wants to be the strict one. The list is a shared mirror. A mirror that lies teaches people to ignore status.

Declines are also data. If three clients decline clause 8, clause 8 is the problem. The tool told you. Listen, fix the template, do not just send the same nonsense to the next person.