Get a document signed without the other person creating an account

People are in the middle of something else. They see 'create user', remember they hate passwords, and put the tab in 'later'. Later is never. You call. They say they could not do it. Both get sour. The document was fine. The door was not.

Internationally it is worse. Norwegian BankID compulsion is one locked door. American 'Sign in with Google, but only Workspace' is another. The other party only needed to say yes to three pages.

Measure: time from email opened to tag. If it is days, it is rarely the law. It is the UI.

A QR on paper to the same link is still a link. It is not ink. It is a camera pointed at SES.

It points at one file. Fields. Their name, so they know it is not a blast to the wrong human. Expiry. Preferably not forwardable to five colleagues who will all 'handle it'.

An email code cuts guessed addresses. It is annoying. Annoyance is an SES-level control, not a certificate.

HTTPS. Not a shortener you do not control. People fear links. You should too, on their behalf.

If the other side insists on an account because that is how we do it, ask whether that is identity or habit. Habit you can negotiate. Identity is eID.

That you sent it. What it is about. That they do not need an account, if that is true. If it requires BankID, say so before they hit a wall.

A heads-up in a thread you already have: 'link in five minutes from X'. Phishing fear is rational. Work with it, not against it with a brand logo.

A from-name that is a human. 'No-reply platform' is how you lost before they opened it.

Do not hide the expiry. A dead link with no explanation is how they think you are spamming them next time.

The sender needs a place to upload and see status. That is an account. The recipient needs a yes. Different roles. Products that force both into the same funnel have mixed CRM with signature.

If you want them to 'come back and fetch the file later', send them the finished PDF. Do not make their archive a reason to sign up.

Teams with no IT: one sender account is enough. Read the other article. Do not invent a licence for the counterparty in your head.

When they are employees in your org and will send every week. When SSO actually exists. When they asked for a portal. Not when they are a client signing once.

When identity is QES. Then the eID app is the account, in a sense. That is a different track. Do not paste it in as 'create a user with us first, then BankID after'. Double punishment.

When the files are sensitive enough that you do not want magic links in the wild. Then you are in another risk class, and an ads wall may be the wrong place anyway.

Finished PDF to the inbox. Receipt if you have one. Say SES, say not QES, say Acrobat may go yellow if the CA is the house CA.

Not 'log in to download'. They did the job. You owe them bytes.

If they forwarded the link to finance: next time, put finance as copy or as their own recipient with a role. Link chaos is how two people sign as one.

A forwarded link is how three people see a personal field. If finance must come in, give them their own role. Copy with no field if they only need to know. A signer field if they must bind.

'Can you send it to finance too' mid-flow: often void and a new job, or an extra recipient if the tool can stand that without lying about order. Do not Slack the PDF and ask them to just sign in the margin.

CC on the notification email is not a signature. People think they said yes because they saw the subject. They saw a subject.

Measure how many finish without an account against how many bounce on registration, if you have a tool that can do both. The number is more convincing than a theory about traceability. Traceability without finished agreements is an empty dashboard.