Share an Employee Severance Agreement Safely

To share an employee severance agreement safely, start with an approved version, confirm the employee’s contact details, and give the employee an appropriate route to consult their adviser. Keep internal drafting notes separate, record which version was delivered, and preserve the agreed signed document in the employer’s approved record system.

Security should support a fair, understandable process. It should not become a reason to obstruct independent advice, hide a deadline, or prevent someone retaining a document they are entitled to keep. HR and the employer’s lawyer should approve the wording, timing, recipients and signature process for the relevant jurisdiction. This guide covers document handling, not the legal validity or enforceability of a severance agreement.

The practical challenge is usually not sending one PDF. It is controlling several versions across HR, counsel, an employee, an adviser and the people administering payment.

Decide who needs each version

Before uploading anything, divide the material into three groups: internal preparation, the offer intended for the employee, and the completed agreement. These groups need different audiences. A payroll contact might need payment instructions from the completed agreement without receiving every discussion note. A manager might need a departure date without seeing the detailed negotiation.

Use named roles rather than a broad department mailing list. Confirm who can release the employee-facing copy and who can approve a revision. Avoid making a junior coordinator decide whether a disputed clause is acceptable. Their job is to route the document to the designated approver.

This separation reduces accidental disclosure without asserting that any sharing tool can make a document impossible to forward. A person who can read information may reproduce it. A controlled channel is one part of the process, not a guarantee of secrecy.

Prepare the employee-facing pack

Use a case identifier that makes sense to the authorised team. Avoid putting a dispute allegation or detailed compensation amount in the filename or email subject. Those fields may appear in notifications or shared calendars outside the document itself.

Check the employee’s name, employer entity, attachments, referenced schedules and page count. Verify that the file contains the approved offer rather than an internal draft with similar naming. Open it from the release location rather than relying on a recent-files shortcut. A shortcut can point to yesterday’s working copy.

Provide a short cover message stating what the pack contains, who can answer procedural questions and how revisions will be communicated. Include dates only after HR or counsel approves them. Do not invent a universal review period. Countries and circumstances differ, and a technology workflow cannot replace the applicable legal requirements.

If the pack includes multiple files, add a one-page manifest. Mark which document is the agreement, which document is explanatory, and which attachments form part of the proposal. That prevents an employee treating an unsigned explanation as the agreement or missing a schedule that matters.

Allow the right adviser to participate

Ask the employee how their authorised adviser should receive the document, subject to the organisation’s approved process. Confirm adviser details through the appropriate contact, rather than adding an address copied from an unverified message. Record consent or authority where required by the process.

An adviser may need to download, annotate or print the file. Discuss those needs before imposing restrictions. If view-only access prevents meaningful review, offer an approved alternative. The answer is not to weaken every control for every recipient; it is to match controls to the actual review task.

Acas explains that confidentiality provisions can have exceptions; blanket silence is not an appropriate assumption. Acas: confidentiality in settlement agreements Ask counsel to determine permitted disclosures instead of encoding a broad prohibition in the delivery message.

Keep adviser communications distinct from internal employer discussion. If a portal supports comments, test who can see them with harmless sample material. If visibility cannot be demonstrated, use a separate approved discussion channel. Do not assume a comment marked private is inaccessible to other participants.

Release one identifiable version

Give every released version an unambiguous identifier and a short revision note. A date alone is insufficient when two revisions are issued the same day. Record the identifier in both the release register and the employee-facing message.

For an HR-approved review workflow, SendNow can restrict the agreement to specified recipients; adviser access should be authorised separately.

When a correction is needed, explain which version supersedes the earlier one. Do not silently replace the document and expect everyone to notice. A recipient may already have saved a copy. Ask the coordinating parties to acknowledge the replacement, while recognising that acknowledgement is not evidence that every older copy has disappeared.

Use this register to keep the workflow coherent, not to monitor the employee’s behaviour. A page view or download event does not establish understanding, agreement, acceptance or legal consent.

A fictional release mistake caught in review

Imagine an employer preparing a departure agreement for a fictional employee, Maya. HR has a file called Offer-v3 and counsel has a file called Offer-v3-review. A coordinator initially selects the review file because it was edited most recently.

The release checklist catches two problems. The selected file includes a comment about negotiation strategy, and its appendix belongs to another draft. The coordinator stops delivery and asks the approver to export a clean employee-facing version. They name it Case-204-Offer-04 and record its page count and included schedules.

Maya later supplies her adviser’s contact through the established HR conversation. The coordinator confirms the approved sharing route and provides the same identified version to the adviser. A revision follows, so HR issues Offer-05 with an explicit note that Offer-04 has been superseded.

The lesson is the sequence: approve, identify, inspect, release, then record. Nothing in this fictional example proves that a provider has special HR functionality, that the agreement is legally effective, or that forwarded copies can be recovered.

Separate signing from access activity

Use the employer’s approved signing process. Do not treat a document-sharing link as an electronic-signature system unless the required signing functionality has been verified and approved. Access controls and signatures solve different problems.

Before signing starts, confirm the version, signatory identities and any required schedules. If a clause changes during the signature process, stop and ask the authorised owner how to restart. A partly signed file and a revised unsigned file should not be combined informally to create a supposed final agreement.

Keep the completion evidence that the signing process provides, but understand its scope. It may identify actions and timestamps; it does not automatically establish that every legal condition has been met. Counsel should decide which evidence matters for this case.

Provide the employee with the appropriate completed copy through the agreed route. Record who owns the employer’s authoritative record. Do not leave that record solely in the departing manager’s mailbox or a coordinator’s personal downloads folder.

Run a harmless delivery rehearsal

Before releasing a real agreement, send a sample pack to test identities representing the employee and the adviser. Use invented names and clearly marked test content. Check the recipient experience on a phone as well as a computer, because someone handling a departure may no longer have routine access to their work laptop.

The rehearsal should answer practical questions. Does the notification reveal an unnecessarily sensitive filename? Does the recipient understand how to open the pack? Are schedules visible without navigating an internal folder? Can an approved adviser obtain the copy they need? Does the sender know how to handle an expired session without granting broad access?

Record a short result against the intended configuration. If the platform changes, repeat the relevant checks. A test performed on a public sample link does not validate a restricted employee pack with different permissions. Likewise, an administrator seeing all files does not establish what an external recipient can see.

Decide who will cover procedural support if the coordinator is absent. Give that backup person the release register and authority boundaries, not unrestricted access to unrelated personnel files. Clear support ownership prevents an urgent access issue becoming a chain of forwarded attachments.

This rehearsal is an editorial recommendation, not a claim that any particular product was tested. Use the existing employer-approved system, and keep the sample separate from the actual employment record.

Handle access problems and incorrect recipients

If the employee cannot open the file, check the exact error and intended recipient before resending. A spelling mistake in an email address, an old session or an unsupported viewer may be the cause. Avoid repeatedly broadening access while guessing.

If the wrong person receives the agreement, stop further distribution, contain access where possible and notify the organisation’s designated incident owner. Preserve the basic facts: file, version, recipient, delivery method and time. Do not delete the release register to conceal the error.

Contacting the recipient and requesting deletion may help, but it cannot guarantee removal of copies. HR, security and counsel should decide the next steps, including any applicable notification duties. Avoid making assurances to the employee before the facts are established.

Finally, review working copies and access according to the employer’s retention schedule. A record needed for an employment matter should not be deleted simply because a link expires. Conversely, a contractor who helped deliver the pack should not retain indefinite access without a continuing role.

Frequently asked questions

Can I make the agreement non-forwardable?+

You cannot guarantee that readable information cannot be copied. Use appropriate recipient controls and approved instructions while allowing legitimate adviser access.

Should I change the review deadline to match link expiry?+

No. HR or counsel determines the appropriate timeline. Configure the delivery route so it supports that timeline, and resolve access problems promptly.

Does a download prove the employee accepted the agreement?+

No. A download indicates an access event, not legal acceptance. Use the approved signature and agreement process.

Before you proceed

A safe release is traceable and usable: the right approved version reaches the right people, revisions are explicit, and the completed record has an accountable owner. Let HR and counsel govern the employment decision while the document workflow supports it.

Parent guide

• Are Online PDF Tools Safe for Confidential Files?

Related articles

• Transfer Shared Files Before an Employee Leaves

• Check Whether a Document Request Is Genuine

• Password-Protected PDF or Secure Link?

Sources and editorial disclosure

Primary documentation reviewed October 13, 2026. Worked examples are fictional illustrations. Checklists and decision frameworks are editorial recommendations; product-specific facts are linked to official documentation. These guides do not claim that signed-in product tests or customer projects were performed.

• Acas: confidentiality in settlement agreements

VDR Directory is published by the team behind SendNow. This ownership is relevant when evaluating any product mention. Stock photos illustrate general context; they do not demonstrate software features or identify actual affected people. Controls and tool availability depend on the provider, edition, version, device and configuration. No guide guarantees confidentiality, regulatory compliance, acceptance of altered documents, or search rankings.