Every event knows its context
Instead of a folder of files, you get a sequence of events. Each one answers: what happened, when, with which documents — and what has to happen next.
- Stages in your own wordsDiscovery, Hearing, Order. Or Details, Payment, Registry. Each trail uses the language of your work.
- Documents where they belongReceipts sit on the payment event, the order sheet on the hearing — fully searchable, versioned and tagged.
- Notes, public or internalKeep internal notes for your team and share only what the client should see.
- A dashboard for each trailEvents, active reminders, documents and last activity at a glance. Search and filter by stage.
Token advance & 1st instalment received
Both transfers verified and credited.
Internal note: seller wants registry before 15 Sep.
Every step keeps its paperwork
Tags, a note and the documents themselves, attached to the moment they belong to. The signed agreement sits on the day it was signed — not in a folder somewhere.
Reminders, and steps that wait their turn
Every upcoming step carries its reminder, shown a few days ahead. Steps that depend on another say so — Waits for: Mutation applied for in the municipal records — so the order of work is never in someone's head.
Done, pending, and the proof for each
"6 of 14 complete · 8 pending", the next item and its date, and every finished item linked to the event and documents behind it. Reopen anything that turns out not to be done.
