MirmiCovered case
Business decision
The team acts within its permissions, with no mandatory Legal handoff.
Legal productivity · Legal departments
Reduce repeated approvals. Focus Legal on high-value decisions.
Mirmi turns past decisions, policies, analyses and agreements into usable legal memory. Teams move known work forward within the approved framework; Legal receives exceptions with their sources, context and the right decision path.
Less recurring work to process again, more capacity to advise, negotiate and decide.
- Known requests handled within the framework
- Legal capacity reserved for exceptions
- Internal memory and applicable law
- Traceable exceptions, decisions and sources
Governance model · explanatory view
From approved framework to an actionable decision
Approved memory and framework
Legal organises positions, policies, sources, thresholds, roles and approval paths.
- Positions
- Thresholds
- Workflows
Outside the framework
Targeted approval
Legal or the designated approver receives the case, its sources and the reason for escalation.
Decision recorded
The action remains traceable. An exception becomes a reusable rule only after explicit qualification.
Legal’s role
Govern recurring decisions instead of reapproving every request.
The legal department makes known work reusable, sets the limits of autonomy and retains control where its judgement creates the most value.
Positions
Define what is standard, acceptable with conditions, rejected or reserved for judgement.
Permissions
Tie available actions to the applicable template, score, role and workflow.
Routing
Send exceptions to Legal or a designated approver such as Finance, Security or the DPO.
Qualified memory
Keep decisions and their sources without automatically turning an exception into a new rule.
External legal intelligence
Your internal practice does not exist outside the law.
Precedents show what the company has done. When the question calls for it, Mirmi complements them with sourced legal research to place the decision within the applicable framework.
External intelligence informs the lawyer; it does not replace legal doctrine, risk assessment or the human decision.
Laws and regulations
Identify the texts applicable to the clause, obligation or sector being reviewed and retain the references useful to the analysis.
Case law and reasoning
Connect a question to relevant decisions, distinguish what supports or weakens a position and keep sources verifiable.
International context
Qualify jurisdiction, mandatory rules and contextual differences when a contract or transaction goes beyond the French framework.
From precedent to permission
Comparable evidence, without confusing evidence and authorisation.
Mirmi places internal decisions back in context: request type, source document, change, status and decision rationale.
That memory informs the analysis. Authorisation remains determined by the approved framework and the capabilities returned by the server.
Decision chain
Four explainable layers
- 01
Qualified precedents
Each reference keeps its own similarity score and context.
- 02
Change score
One global score applies to the analysed change, not to the best precedent.
- 03
Authorised actions
The workflow exposes the available capabilities: accept, reject or escalate depending on the case.
- 04
Human decision
The user acts; the decision and its supporting evidence remain traceable.
An exception is not a rule
A one-off approval remains contextual. Reusing it as an approved position requires explicit qualification.
Controlled delegation
Take Legal out of repeated loops without losing control.
The system separates covered cases, requests for help and mandatory exceptions so Legal time is spent on decisions that genuinely require its expertise.
Autonomy
The covered case moves
The business team decides with the intended evidence and permissions. No Legal ticket is created by default.
Support
Legal remains available
Even when an autonomous action is authorised, the user can request advice if the workflow permits it.
Exception
The right approver steps in
A below-threshold, sensitive or out-of-template deviation follows the configured approval path.
Measurable productivity
Connect autonomy, turnaround time and Legal capacity.
The scorecard tracks volumes, resolutions, handoffs and turnaround times over a defined period to show where legal memory gives time back to Legal.
Cases handled
Volume of changes analysed and decisions made over a selected period.
Resolution without escalation
Share of cases closed by teams within the permissions available to them.
Legal handoffs
Number of cases sent to Legal, with the reason and related workflow.
Time and capacity
Observed turnaround times, exception reasons and effort involved connect workflow performance with Legal capacity.
Frequently asked questions
Control does not mean systematic approval.
01Does Mirmi replace the legal department’s judgement?
No. Mirmi structures memory, analysis and routing. Legal keeps new, sensitive or ambiguous decisions and defines the framework in which teams can act.
02Does the score constitute an authorisation?
No. The score qualifies the overall change. Permissions come from the applicable template and workflow, then a person makes the decision.
03Does an approved exception automatically become a rule?
No. It remains attached to its context. Promoting it to a reusable precedent or position requires explicit qualification.
04Does Legal necessarily see every case?
No. A covered case can be handled without creating a Legal task. The decision remains traceable according to configuration, and Legal can still be involved whenever the workflow permits or requires it.
05Does Mirmi rely only on our precedents?
No. Internal memory carries your actual practice; external legal research can complement it with laws, regulations, case law and international context. Sources remain visible and the lawyer retains the final assessment.
06Can other approvers be involved?
Yes. A workflow can route a case to the designated role, such as Legal, Finance, Security or the DPO. Roles and permissions depend on the approved configuration.
07Does this page cover CLM integration?
No. It describes governance, delegation and decision control. Connections to a CLM or document tools are presented separately under Mirmi Connect.
Start with one recurring decision
Make known work reusable. Reserve Legal for decisions that deserve it.
Start with one request family, its decisions, sources and approval paths to build a first measurable workflow.