How Sealio works
The building blocks of document collection in Sealio.
This page describes how Sealio is designed to work. The features are Planned and will be marked available here as they ship.
Sealio uses one model for one-off work (for example, a study permit application) and recurring work (for example, monthly bookkeeping).
| Term | What it is |
|---|---|
| Client | A person or business your firm works with. Clients belong to your firm; no other firm can see them. |
| Checklist | A reusable list of documents to collect, optionally grouped into sections, such as Identity and Income. |
| Request | A checklist sent to a client, with a due date and optionally a period such as 2026-Q1. Each request is tracked, reminded and reviewed on its own. |
| Case | An optional folder that groups requests, notes and assignees around one piece of work: an application, a loan file, a claim. |
| Schedule | An optional rule that sends a new request every period (monthly, quarterly or yearly), so recurring work runs itself. |
The request lifecycle
- Draft: you choose a checklist or add items, pick the client and a due date.
- Sent: the client gets a secure link. No account or password is needed.
- In progress: the first upload arrives. Each item shows To upload, Uploaded, Accepted or Needs changes.
- Under review: your team accepts each item, or returns it with a reason the client can see.
- Complete: every required item is accepted.
Reviewing documents
Reviewers see the checklist next to the document and use keyboard shortcuts: A to accept, R to return with a reason, J for the next item.