Enforcement officers
Opening a file — the gesture nobody bills
3 min read
A judgment arrives. Someone opens it, reads it, and retypes into the software what they have just read. That gesture appears on no billing line, and yet it is the first of every matter.
A practice never complains about opening a file. The gesture is so ingrained that it is no longer perceived as work: you open, you type, you move on. You have to look at it closely to see what it actually weighs.
The gesture, as it stands
A judgment arrives with its instruction, usually by email. You have to identify the parties, check them against the existing records in case they already exist under a different spelling, carry over the legal characterisation, copy the amounts across, and link the file to the right court. Then you move on to the next one.
Each of those points is simple. None is automatable inside the practice’s own software — Soolus, CDJ 2, Septeo — because those systems are closed. They are approved, secure, entrenched in a profession that offers few realistic alternatives, and they have no commercial reason to open an entry point to a third-party program. This is not an oversight, it is the model.
The result is that the only operator the tool expects is a person in front of a screen.
Three costs, only one of which is measured
Time is the visible cost. It is not the highest.
| What you think you pay | What you actually pay |
|---|---|
| The time an opening takes | Attention that cannot be split |
| One data entry | A possible duplicate, found much later |
| An administrative task | An address error that forces the document to be drawn up again |
The second cost is the duplicate. The same party entered twice, under two spellings, causes no problem on the day it is entered. It causes one the day two case handlers each work on their own version.
The third is the heaviest and the rarest: an error carried from the judgment into the document. There, it is no longer time — it is a document to be drawn up again, with everything that implies in delay and in liability.
What changes when an agent holds the gesture
An agent working inside the practice’s software replaces neither the tool nor the person. It takes over the part of the gesture that is pure transcription: reading what has arrived, preparing what has to be opened, flagging whatever is not self-evident.
That last part is the one that counts. An uncertain address, a characterisation that calls for judgement, an amount that does not match the operative part: the agent stops and says so, rather than deciding.
The rule is simple. Anything that is a decision goes up. Anything that is transcription stays down.
And service of the document was never in play. It stays with the practice — with the commissaire de justice, or with the clerc significateur appointed by the First President of the Court of Appeal on the application of the office holder — and no agent goes near it.
Why this is not an integration problem
We are often asked whether the software vendor will eventually open an interface. The honest answer is no, and there is no reason for that to change: a vendor firmly established in a regulated profession has no interest in letting a third party work inside its tool.
That is precisely why the problem is solved elsewhere. Not by waiting for an opening that will not come, but by having the agent work the way the person works — in the tool as it is, on a machine the practice controls.
What an agent actually does in a practice, with no practice named, is described in our resources. The operational detail is given in conversation.
Does any of that sound familiar?
If you work in a regulated profession and spend your days inside software that will not automate, the best next step is a conversation.