LossStack Office
LossStack Sign
Send, sign, track, and store claim-related documents without leaving the claim.
LossStack Sign is built directly into LossStack Office. Prepare a document, add recipients, and send for signature — all without switching to another platform or exporting files.
How it works
Electronic signatures
Send documents for electronic signature directly from the claim record inside LossStack Office. Recipients sign from any device without creating an account.
Reusable document templates
Build reusable templates for common claim documents — authorization forms, scope agreements, completion certificates, and contractor documents. Populate fields from claim data and send in seconds.
Multiple recipients
Route documents to multiple signers — clients, contractors, or other parties — in any sequence or in parallel. Each recipient receives their own signing link.
Automated reminders
LossStack Sign automatically follows up with recipients who have not signed. No manual reminder emails. Signing progress stays visible in the claim record.
Everything included in LossStack Sign
Electronic signatures
Legally binding e-signature without leaving LossStack
Reusable document templates
Build once, send many — pre-fill from claim data
Multiple recipients
Sequence or parallel routing to any number of signers
Signature status tracking
See what is sent, opened, and signed in real time
Automated reminders
Follow-up reminders sent automatically to pending signers
Signed-document storage
Completed, signed documents stored in the claim record
Claim-linked audit history
Every send, view, and signing action logged to the claim
Direct access from LossStack Office
No separate platform or tab switching required
Client and contractor workflows
Covers client approvals, contractor agreements, and internal documents
Directly from the claim record
LossStack Sign is not a separate product. It lives inside LossStack Office and is accessed directly from the claim. Every document sent, signed, or stored is connected to the claim record — so the complete signing history is always in context, not in a separate signing platform.
Completed, signed documents are stored in the Claims Library and visible to authorized team members. The audit trail is part of the claim — not a separate log to export.