Vigilance
Consistency checks on a succession dossier
Twenty-two reasons to flag something, twelve of them checks that re-read the dossier for what does not add up. None corrects anything, none blocks: they show you, and you decide.
- 22 reasons to flag
- twelve of them checks reading the dossier's documents against each other
- Nothing to tick off
- a flag disappears on its own the day its cause is gone
- No blocking
- flags inform you, they lock no action and correct nothing
How it works
- 01Incoming documents feed the dossier
- 02Twelve checks re-read what they produced
- 03What does not add up is flagged, most urgent first
Regorus detects and flags, and corrects nothing itself
Each time a dossier is opened, Regorus re-reads what the documents produced and compares the data: the assets, the heirs, the names read on identity documents, the mortgage entries against the recorded debts, and the documents themselves. No duplicate is merged, no amount rewritten.
This is not excessive caution, it is the only workable design. Two assets that look alike may be a duplicate or two genuinely separate accounts at the same bank, and nothing in the documents settles it for certain. You decide, in one click, from the relevant tab.
Three alert levels, so the urgent stays visible
Twenty-two reasons can flag something to you, from a letter left without a reply to an heir link about to expire. Out of the twelve consistency checks, only one raises the top level: a change of account number on an heir's bank details. All the others ask for a look, or are simply noted.
The reason is simple: a tool that alerts on everything alerts on nothing. Treating a probable duplicate and a substituted bank account with the same intensity teaches a practice to ignore both.
A flag closes itself once its cause is gone
Most flags are not events, they are situations. « This letter has been awaiting a reply for 21 days » stops being true the day the reply arrives. Regorus therefore recomputes the real state of the dossier on every pass, adds what is missing and removes what no longer applies.
In practice the counter falls without anyone clicking. A practice coming back from three weeks off does not find three weeks of stale messages, it finds today's state.
An ordinary alert list
- You have to open every line by hand to bring the counter down.
- Three weeks away means three weeks of backlog to sort.
- A point already settled stays on screen until someone tidies up.
With Regorus
- The counter falls as soon as the situation stops being true.
- Back from leave, the screen shows today's state.
- « Read » is personal; « dismissed » applies to the whole practice.
You choose how you are told
Three channels exist and they do not carry the same things. Email only sends an immediate alert for what warrants one, once per point and per person, never between 8 pm and 7 am, with a daily cap. Everything else arrives in a digest, grouped by dossier.
- What if two colleagues want different things?
- Each person sets their own delays and their own channels. On a shared dossier, it is the more sensitive of the two settings that triggers the alert.
- And if Regorus goes down?
- An outside probe queries the service every 5 minutes and emails us if it stops answering. It is hosted somewhere other than the product, so that it does not go down at the same time.
Getting started
- 01Nothing to switch on: the checks run from the first dossierRegorus
- 02Each person chooses after how many days they want to be told a dossier has stopped movingeach member, once
- 03Each person picks their channels in their settingseach member
The default is 21 days, and the same setting exists for a letter draft left waiting and for an heir's collection that has stalled. These delays are personal rather than collective: two colleagues on the same dossier may want to be disturbed at different points.
Frequently asked
Are these checks done by artificial intelligence?
No. They are exact comparisons: names, amounts, account numbers, file fingerprints and dates. AI runs upstream, to read the documents, and what it produces is precisely what these checks re-read.
Can a flag block a send or an action?
None of them. Flags inform, they never lock anything. If you know a change of bank details is legitimate, you clear it in one click and carry on.
How many messages does a practice get per day?
It depends on the number of open dossiers, and we have no honest average to offer. What we can say: immediate email alerts are capped, never sent at night, and everything else arrives in a single digest per dossier.
Can I silence a flag I have already dealt with?
Yes, in one click. It does not come back until the situation has gone and returned. « Dismissed » applies to the whole practice, so a colleague will not see it again either, whereas « read » applies to you alone.
Do the heirs receive these alerts?
Never. These messages only go to members of the practice, and never to a third party. An heir receives a message only if someone at the practice wrote it, read it and sent it.
What deserves a second look is flagged, and nothing else.
Twenty-two reasons, one single top-level alert, and flags that disappear as soon as their cause is gone. You see what needs a decision, not an activity log.
See also
- Dossier progress5 phases, 60 milestones, and a filing deadline computed from date to date, with its calculation sheet. Uploading a document ticks the matching milestone.
- Devolution and peopleTen kinds of relationship, four capacities under a will, legal entities: every beneficiary is qualified, and statutory devolution is proposed to you.