● Public sector — Legal affairs
The AI agent for public sector lawyers: sourced research, monitoring under control
Finding the applicable case law, keeping up with texts that change constantly, drafting a first version of an act: this documentary work takes up a considerable share of legal officers' time — without being the analysis the authority actually expects. Your AI agent absorbs the research and the monitoring, with sources cited. Hosted in France — on local inference or an isolated resource — the data stays under control. The AI agent assists, the legal officer decides.
Hosted in France
Public data protected
GDPR & AI Act: governed deployment
Human oversight
Updated on
Deployed in a few weeks
Legal assistant · hosted in France
Our authority wants to raise the threshold below which a works contract is exempt from publication. What is the state of the applicable law and what are the conditions?
State of the law (up to date). The exemption from a formal procedure for works contracts applies below the threshold set in the Public Procurement Code, raised by decree for certain operations.
Conditions: compliance with the principles of public procurement (equal treatment, transparency), no artificial splitting of the contract, and verification that the price is reasonable. Three references cited, including a recent administrative case-law decision.
⛓ Source · the authority's legal databases + consolidated texts cited
Conditions: compliance with the principles of public procurement (equal treatment, transparency), no artificial splitting of the contract, and verification that the price is reasonable. Three references cited, including a recent administrative case-law decision.
⛓ Source · the authority's legal databases + consolidated texts cited
Has there been any recent regulatory change to that threshold?
Monitoring signal. A recent decree has changed the threshold for works contracts; the consolidated version applicable at your date is cited. Note: a draft text out for consultation could change it again — worth watching before the council votes.
I am preparing a sourced briefing note for your approval.
✎ Action · sourced note ready for review — the legal officer approves and signs
I am preparing a sourced briefing note for your approval.
✎ Action · sourced note ready for review — the legal officer approves and signs
Local inference · no data outside the EU
Data hosted in France
Sovereign by designLocal inference or hosting in France
GDPR & AI Act: governed deploymentTraceability & human oversight
TurnkeyDesigned, installed and operated for you
The legal officer decidesThe agent assists, never rules alone
✦ In brief
In a legal affairs department, a Blue Lemon Agent agent searches and summarises case law, doctrine and applicable texts, with sources cited, tracks regulatory developments in your fields and prepares draft acts and pleadings. It runs on local inference or is hosted in France: no public data is exposed to a foreign service, architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity. The time saved is redirected towards higher-value legal analysis. The agent prepares and sources; the opinion stays with the legal officer. Live within a few weeks.
100%
hosted in France in the target architecture
0
transfer outside the EU in the target architecture
9
uses ready to deploy on this scope
0
decision taken without human approval
Reference points describing our offer, not results measured at a client. The scale of the gain is confirmed by a pilot on your own scope.
The context
Why AI matters to public sector lawyers — and why they hesitate
The law applicable to local authorities and public bodies changes constantly, and response times are getting shorter. But available time is mechanically reduced by documentary research and monitoring — and the data handled engages the liability of the public body.
! The issue
The legal department is caught between elected members and directorates who want reliable, fast answers, and an ever-growing documentary workload (case law, doctrine, consolidated texts, regulatory monitoring). Yet most consumer AI solutions amount to entrusting litigation files, draft council decisions and sensitive data to a third party, often hosted outside Europe and subject to the Cloud Act.
✓ Our answer
AI is only of interest to a public body if it is sovereign and confidential by design. Local inference or an isolated resource hosted in France, systematic human oversight, decisions reserved to the legal officer: the time saved on research is never paid for in lost sovereignty. The aim is not to replace the legal officer, but to give them back time for analysis — in the service of continuity and equal treatment.
The decisive point
Sovereignty of public data: compliance & control
A legal department handles data that engages the authority's liability. Here is how the architecture of our agents protects it, file by file.
Local inference
The agent can run on a machine belonging to the authority: no document leaves the network, nothing passes through a cloud.
Hosting in France
Otherwise, a dedicated and isolated resource, hosted in France under French law — your data: processing and access within the European Union targeted by the architecture.
Reduced extraterritorial exposure
Exposure of the data to the Cloud Act and FISA 702 is reduced by design; location alone does not guarantee immunity.
One isolated resource per entity
No pooling of data: an environment strictly dedicated to your authority or institution.
Encryption & controlled access
Encryption in transit and at rest, role-based access (RBAC), strong authentication and logging.
AI Act: governed deployment
An agent strictly in support; no opinion issued automatically; traceability and human oversight from end to end.
What depends on the architecture chosen These points are not general guarantees: they are settled deployment by deployment, in the quotation.
- The applicable location is that of the architecture set out in the quotation and verified before commissioning.
- Local execution is announced only for the configuration explicitly described and accepted in the quotation.
- The applicable isolation depends on the deployment mode set out in the quotation; no dedicated isolation is presumed.
- The encryption mechanisms in transit and at rest, their components and key management are those documented for the architecture chosen.
- Roles and permissions are configured and accepted for the identities and systems actually connected.
- The events logged, their content, their retention period and who may access them are defined for the deployment chosen.
For the most sensitive data, SecNumCloud and HDS options are available depending on your requirements. A single architecture is designed to answer both the GDPR and extraterritorial exposure. Designed for deployment in line with the GDPR and the AI Act, after the processing, roles and context-specific risks have been assessed.
Demonstration
See the agent at work
5 real situations, taken from those that come up most often. Pick one: the exchange unfolds as it would in your organisation.
A scripted demonstration. These exchanges show how the agent behaves — its sources, its refusals, what it leaves to your teams. Nothing is sent from this page, no model is queried here, and the matters named are fictional. That is precisely what we promise your data.
The behaviours shown here — monitoring, automation rules, routing and reminders — are configured with you during deployment, from your tools, your rules and your thresholds.
The architecture points named in these exchanges — location, local execution, isolation, encryption, role-based access, logging — are not a guarantee attached to the demonstration: they are those of the architecture set out in your quotation, and verified before commissioning.
The public body in this demonstration
Fictional public bodyVallée-Haute County Council — 214,000 residents, legal affairs department
- Sector
- County council — social care and independence, secondary schools, county roads, fire and rescue service; a legal affairs department shared by the 14 operating departments
- Headcount
- 2,100 staff, of whom a legal affairs department of 5: 3 lawyers, a director and an assistant; no post dedicated to public procurement
- Public served
- 214,000 residents, 14 internal departments and 3 satellite bodies — fire and rescue service, county laboratory, attractiveness agency
- Order of magnitude
- 740 referrals a year — 410 legal questions from the departments, 190 draft instruments and agreements reviewed, 96 pre-litigation files, 44 defence statements; 6 sittings of the county assembly; 11 watch areas
- Tools in place
- Subscription legal database, document management system, resolutions software, eleven years of opinions filed by department — the agent connects in read-only, nothing is replaced or migrated
- Who decides what
- The director of legal affairs signs the opinions; the president of the county council signs the instruments; defence statements go out under the director's signature, after review by the council's counsel
- The points to improve
- A referral waits 12 days for its first answer; research takes 3 h 30 of the 5 h 50 an opinion demands; 7 of the 11 watch areas have not been reopened for six months; and 34 of the 190 draft instruments reviewed last year cited a text of which a later version already existed
At Vallée-Haute, three lawyers serve fourteen departments and three satellite bodies. Questions arrive faster than they leave, the watch comes after the files, and half the time spent on an opinion goes to documentary research before the first line of analysis is written. The agent runs in local inference on a machine of the county council, reads the eleven years of opinions without ever writing to them, and sends nothing out without the signature of the director of legal affairs. The exchanges below cover one year, from the reopening of the watch to the review presented to the executive committee.
This public body, its figures and the exchanges that follow were invented for the demonstration. They illustrate a common situation; they describe no real service.
Legal assistant · hosted in France
I reread your eleven years of opinions over the weekend — 2,340 opinions issued, 1,870 draft instruments reviewed, 11 watch areas — and I draw from them two gaps your department was carrying without having the time to look at them.
The first gap, measured: 34 of the 190 draft instruments reviewed last year cited a text of which a later version already existed on the day of the review. This is not an analysis error: it is a legal database reloaded once a month while the texts themselves move continuously. Three occupation agreements for county buildings and two grant rulebooks referred to wording that had been replaced.
The second gap: 7 of your 11 watch areas had not been reopened for six months. Here too it is not a matter of method: it is three lawyers for 740 referrals, and the watch comes after the file that is waiting.
What that costs today, on the three items you can check in your own records:
· Research takes 60 % of the time of an opinion — 3 h 30 of the 5 h 50 an opinion demands, from the referral to the signature. A referral is the question an operating department addresses to the legal affairs department; the opinion is the written, signed answer that commits the council.
· Following one regulatory watch area: 22 % of the time that area demands, that is 1 h 46 out of 8 hours a month. Regulatory watch means tracking the texts that change in one area, so that the answer given yesterday is still right today.
· A first draft instrument or defence statement: 30 % of the time of the document.
What I propose, and it is not an intention — it is already done: I reopened the 11 areas overnight and ran them back over the last six months. 17 changes concern you, each with the consolidated version applicable at your date, the date it came into force and the list of your earlier opinions it touches — 9 opinions to re-flag, and the 9 re-flagging notes are written.
What I do with the three items once the watch is held: research drops from 60 % to 18 % — from 3 h 30 to 1 h 03; following an area from 22 % to 8 % — from 1 h 46 to 38 minutes; a first draft from 30 % to 12 %. Your department keeps what it alone can do: qualify, arbitrate, sign.
The next step takes thirty minutes: tomorrow morning you read the 9 re-flagging notes, which I hand over already written and sorted by recipient department. The director signs them and they go out the same day — it is that signature which makes them the council's opinion, and it is the only gesture I leave to you. legal-memory_11-years-of-opinions-indexed.pdf2,340 opinions indexed, 34 drafts to re-flag, 9 notes written
⛓ Sourced · 11 years of opinions, 1,870 draft instruments reviewed, 11 watch areas run back over 6 months, consolidated versions and their dates
The first gap, measured: 34 of the 190 draft instruments reviewed last year cited a text of which a later version already existed on the day of the review. This is not an analysis error: it is a legal database reloaded once a month while the texts themselves move continuously. Three occupation agreements for county buildings and two grant rulebooks referred to wording that had been replaced.
The second gap: 7 of your 11 watch areas had not been reopened for six months. Here too it is not a matter of method: it is three lawyers for 740 referrals, and the watch comes after the file that is waiting.
What that costs today, on the three items you can check in your own records:
· Research takes 60 % of the time of an opinion — 3 h 30 of the 5 h 50 an opinion demands, from the referral to the signature. A referral is the question an operating department addresses to the legal affairs department; the opinion is the written, signed answer that commits the council.
· Following one regulatory watch area: 22 % of the time that area demands, that is 1 h 46 out of 8 hours a month. Regulatory watch means tracking the texts that change in one area, so that the answer given yesterday is still right today.
· A first draft instrument or defence statement: 30 % of the time of the document.
What I propose, and it is not an intention — it is already done: I reopened the 11 areas overnight and ran them back over the last six months. 17 changes concern you, each with the consolidated version applicable at your date, the date it came into force and the list of your earlier opinions it touches — 9 opinions to re-flag, and the 9 re-flagging notes are written.
What I do with the three items once the watch is held: research drops from 60 % to 18 % — from 3 h 30 to 1 h 03; following an area from 22 % to 8 % — from 1 h 46 to 38 minutes; a first draft from 30 % to 12 %. Your department keeps what it alone can do: qualify, arbitrate, sign.
The next step takes thirty minutes: tomorrow morning you read the 9 re-flagging notes, which I hand over already written and sorted by recipient department. The director signs them and they go out the same day — it is that signature which makes them the council's opinion, and it is the only gesture I leave to you. legal-memory_11-years-of-opinions-indexed.pdf2,340 opinions indexed, 34 drafts to re-flag, 9 notes written
⛓ Sourced · 11 years of opinions, 1,870 draft instruments reviewed, 11 watch areas run back over 6 months, consolidated versions and their dates
Eleven watch areas for three lawyers is precisely the problem. What do you report, and how often?
The 11 areas are run every night, and I report only what touches a file, an instrument or an opinion of the house — 17 changes over six months, not 400 alerts.
How the sorting is done, and it is verifiable: a change is reported only if it touches one of your 2,340 opinions, one of your 190 draft instruments in progress, or one of the 11 areas you designated. Every alert carries three things: the text in the consolidated version applicable at your date, the date it came into force, and the named list of your own outputs it touches.
What running back the last six months gave, area by area:
· Social care and independence: 6 changes, of which 2 touch 4 of your grant rulebooks.
· Public procurement: 4 changes, including the amount below which a contract may be awarded without prior advertising or competition — I give you the amount in force at your date and the consolidated version carrying it, not a figure from memory.
· Public property and occupation: 3 changes, including the one touching your 3 building occupation agreements.
· The other 8 areas: 4 changes, none touching a file in progress — and I tell you so, because a watch that reports nothing is information, not silence.
The rhythm I propose, and you set it to the word: a one-page note every Monday morning, an immediate alert only when a text touches a file whose deadline is running — a pre-litigation file, a statement to be filed, a resolution on the agenda of a sitting. Over the six months run back, that trigger would have fired three times, and all three rightly.
The time that moves: following one area goes from 1 h 46 to 38 minutes a month, across 11 areas and 12 months — 149 hours returned to analysis.
The next step I propose: add the twelfth area your mandate plan announces — the environmental transition of secondary schools. Nobody follows it today, it will weigh 14 resolutions over the next two years, and I open it the night your agreement comes. regulatory-watch_11-areas-17-changes.pdf17 changes retained, 9 opinions to re-flag, 3 immediate alerts
⛓ Sourced · 11 areas run back over 6 months, consolidated versions and dates of entry into force, register of opinions and drafts in progress
How the sorting is done, and it is verifiable: a change is reported only if it touches one of your 2,340 opinions, one of your 190 draft instruments in progress, or one of the 11 areas you designated. Every alert carries three things: the text in the consolidated version applicable at your date, the date it came into force, and the named list of your own outputs it touches.
What running back the last six months gave, area by area:
· Social care and independence: 6 changes, of which 2 touch 4 of your grant rulebooks.
· Public procurement: 4 changes, including the amount below which a contract may be awarded without prior advertising or competition — I give you the amount in force at your date and the consolidated version carrying it, not a figure from memory.
· Public property and occupation: 3 changes, including the one touching your 3 building occupation agreements.
· The other 8 areas: 4 changes, none touching a file in progress — and I tell you so, because a watch that reports nothing is information, not silence.
The rhythm I propose, and you set it to the word: a one-page note every Monday morning, an immediate alert only when a text touches a file whose deadline is running — a pre-litigation file, a statement to be filed, a resolution on the agenda of a sitting. Over the six months run back, that trigger would have fired three times, and all three rightly.
The time that moves: following one area goes from 1 h 46 to 38 minutes a month, across 11 areas and 12 months — 149 hours returned to analysis.
The next step I propose: add the twelfth area your mandate plan announces — the environmental transition of secondary schools. Nobody follows it today, it will weigh 14 resolutions over the next two years, and I open it the night your agreement comes. regulatory-watch_11-areas-17-changes.pdf17 changes retained, 9 opinions to re-flag, 3 immediate alerts
⛓ Sourced · 11 areas run back over 6 months, consolidated versions and dates of entry into force, register of opinions and drafts in progress
Our pre-litigation files and our defence statements are the most sensitive material we hold. Where do they go when you read them?
They go nowhere. I run in local inference on a machine of the county council, and nothing I read leaves your network.
Local inference means the model computes on your machine: the text of a defence statement or a pre-litigation file crosses no external network to be processed. If the council prefers not to host a machine, the other route is an isolated resource hosted in France, dedicated to Vallée-Haute — no pooling with another authority, which is the condition of the continuity of your service.
What that changes, point by point:
· Your files train no model, neither ours nor a third party's.
· I work read-only on your document management and your resolutions software, and the technical account through which I read has no right to write — that is stronger than a promise, because it is checked with one command.
· Encryption in transit and at rest, role-based access — rights follow the function: a lawyer of the legal affairs department opens pre-litigation files, an operating department opens only its own referrals. 17 roles for the 14 departments and the 3 satellite bodies, and the log shows 0 access outside role since go-live.
· Pre-litigation files form a separate perimeter: only the director and the three lawyers have access, and every opening is logged by name.
· Hosting in France, under French law, architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity.
The gesture that stays with a person, and it is what gives the opinion its value: the signature of the director of legal affairs. Everything leading to it, I have already done: the research, the texts in the version applicable at the date of the question, the court decisions handed over in full with the link to the public database where each can be read entirely, your own earlier opinions on the same point, and the drafted opinion. It is the signature that commits the council, and it is the signature that makes the opinion something a department can rely on.
The figure that sums all this up: 0 file document out of the council's network, processing in the EU targeted, over 1,480 traced outputs since go-live.
What I propose: that I keep up to date the register sheet your data protection officer will ask for — hosting, data processed, retention periods, who accesses what. It is asked for once a year and takes three days to rebuild; the first version is already written and you have it as an exhibit. technical-framework_where-the-legal-files-live.pdfLocal inference, read-only, processing in the EU targeted
✎ Framework · deployment architecture, rights of the technical account, access log, first version of the register sheet
Local inference means the model computes on your machine: the text of a defence statement or a pre-litigation file crosses no external network to be processed. If the council prefers not to host a machine, the other route is an isolated resource hosted in France, dedicated to Vallée-Haute — no pooling with another authority, which is the condition of the continuity of your service.
What that changes, point by point:
· Your files train no model, neither ours nor a third party's.
· I work read-only on your document management and your resolutions software, and the technical account through which I read has no right to write — that is stronger than a promise, because it is checked with one command.
· Encryption in transit and at rest, role-based access — rights follow the function: a lawyer of the legal affairs department opens pre-litigation files, an operating department opens only its own referrals. 17 roles for the 14 departments and the 3 satellite bodies, and the log shows 0 access outside role since go-live.
· Pre-litigation files form a separate perimeter: only the director and the three lawyers have access, and every opening is logged by name.
· Hosting in France, under French law, architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity.
The gesture that stays with a person, and it is what gives the opinion its value: the signature of the director of legal affairs. Everything leading to it, I have already done: the research, the texts in the version applicable at the date of the question, the court decisions handed over in full with the link to the public database where each can be read entirely, your own earlier opinions on the same point, and the drafted opinion. It is the signature that commits the council, and it is the signature that makes the opinion something a department can rely on.
The figure that sums all this up: 0 file document out of the council's network, processing in the EU targeted, over 1,480 traced outputs since go-live.
What I propose: that I keep up to date the register sheet your data protection officer will ask for — hosting, data processed, retention periods, who accesses what. It is asked for once a year and takes three days to rebuild; the first version is already written and you have it as an exhibit. technical-framework_where-the-legal-files-live.pdfLocal inference, read-only, processing in the EU targeted
✎ Framework · deployment architecture, rights of the technical account, access log, first version of the register sheet
The buildings department wants to make a county-owned room available to a sports association, free of charge. They referred it to us eight days ago.
The file is built, and I hand it over with the rule in plain terms, the texts in the version applicable today, and the council's four precedents.
The rule, described without jargon: an authority may make an asset of its public property available to an association, including free of charge, but the free use must be justified by a public interest reason and decided by the assembly. What makes the difference between a solid agreement and a fragile one is that the resolution says why — which activity, which public served, which interest for the council — and that the agreement sets the term, the charges borne by each party and the conditions for withdrawal.
What I hand over, and where it comes from:
· The applicable texts in their consolidated version as of today, with the date each came into force — and they re-flag themselves the day they move.
· The administrative court decisions I retained on this point, handed over in full, each with the link to the public database where it can be read entirely. I give you the useful passage highlighted and the whole decision beside it.
· Your four precedents: four free occupation agreements signed by the council over eleven years, with what each provided on term, charges and withdrawal. Two of them carried no withdrawal clause: that is the point I propose to take up.
· The drafted opinion, with the question, the rule, its application to the case, and the three points the director will settle placed at the top.
One point of vigilance, and it comes with its answer: a text under consultation could change the conditions of free use — I have followed it since it opened, and on the day it is published your note updates itself, with the list of the agreements it touches.
The time that moves: research goes from 60 % to 18 % of the time of an opinion — from 3 h 30 to 1 h 03. Across 410 legal questions a year, that is 1,004 hours returned to analysis and advice to the departments. And for the buildings department, the first answer goes from 12 days to 2.
The next step I propose: that I build the draft agreement and the draft resolution right away, on your templates, with the withdrawal clause that two of your four precedents lacked. You have them tomorrow morning, and the item can be tabled for the June sitting. sourced-note_free-use-of-a-council-building.pdfRule in plain terms, dated texts, 4 precedents, 3 points to settle
⛓ Sourced · texts in their consolidated version applicable today, court decisions handed over in full, 4 occupation agreements of the council
The rule, described without jargon: an authority may make an asset of its public property available to an association, including free of charge, but the free use must be justified by a public interest reason and decided by the assembly. What makes the difference between a solid agreement and a fragile one is that the resolution says why — which activity, which public served, which interest for the council — and that the agreement sets the term, the charges borne by each party and the conditions for withdrawal.
What I hand over, and where it comes from:
· The applicable texts in their consolidated version as of today, with the date each came into force — and they re-flag themselves the day they move.
· The administrative court decisions I retained on this point, handed over in full, each with the link to the public database where it can be read entirely. I give you the useful passage highlighted and the whole decision beside it.
· Your four precedents: four free occupation agreements signed by the council over eleven years, with what each provided on term, charges and withdrawal. Two of them carried no withdrawal clause: that is the point I propose to take up.
· The drafted opinion, with the question, the rule, its application to the case, and the three points the director will settle placed at the top.
One point of vigilance, and it comes with its answer: a text under consultation could change the conditions of free use — I have followed it since it opened, and on the day it is published your note updates itself, with the list of the agreements it touches.
The time that moves: research goes from 60 % to 18 % of the time of an opinion — from 3 h 30 to 1 h 03. Across 410 legal questions a year, that is 1,004 hours returned to analysis and advice to the departments. And for the buildings department, the first answer goes from 12 days to 2.
The next step I propose: that I build the draft agreement and the draft resolution right away, on your templates, with the withdrawal clause that two of your four precedents lacked. You have them tomorrow morning, and the item can be tabled for the June sitting. sourced-note_free-use-of-a-council-building.pdfRule in plain terms, dated texts, 4 precedents, 3 points to settle
⛓ Sourced · texts in their consolidated version applicable today, court decisions handed over in full, 4 occupation agreements of the council
The association has already sent a draft agreement of its own. Nobody here has time to read it line by line.
I read it line by line — 14 pages, 31 clauses — and I hand you the reading done: 24 clauses in line with your practice, 5 to discuss, 2 to rewrite, each with the wording I propose.
What the reading gave:
· Term: 12 years, with no early withdrawal clause. Your four precedents cap at 6 years. I have written the withdrawal clause for public interest reasons, with notice, taken from your two most recent agreements.
· Charges: the draft puts major maintenance on the council and day-to-day upkeep on the association. Across your four precedents that is the usual split — I flag it as compliant, not as a discussion point.
· Insurance: the clause provides for no annual certificate. I have written the clause requiring one, and the standard annual reminder letter with it.
· Subletting: allowed without the council's prior agreement. That is the point I place at the top of your note — and the replacement wording is written, aligned on the one you have used since 2019.
· Two references to texts in an earlier wording: I give you the version in force today and the clause rewritten accordingly.
And one check I run systematically: internal consistency across the documents. The floor area stated in article 2 — 340 m² — does not match the attached plan, which shows 386. This is not a question of law, it is a gap between documents, and it would have brought the agreement back after signature. The request for a corrected document is written, ready to go to the association.
What that gives you: reading a draft agreement goes from two and a half hours to twenty minutes of review, and across the 190 draft instruments and agreements the department reviews each year, this is the item where gaps between documents are caught before signature rather than after.
The next step I propose: that I run the same check on the council's 23 occupation agreements in force. They were signed over eleven years, by four different departments, with five wordings of the insurance clause. The comparison is already made and fits on one page: say yes and you have it tonight. document-review_31-clauses-and-a-floor-area-gap.pdf24 clauses compliant, 5 to discuss, 2 rewritten, 1 gap between documents
⛓ Sourced · draft agreement sent by the association, attached plan, 4 occupation agreements of the council, texts in their consolidated version
What the reading gave:
· Term: 12 years, with no early withdrawal clause. Your four precedents cap at 6 years. I have written the withdrawal clause for public interest reasons, with notice, taken from your two most recent agreements.
· Charges: the draft puts major maintenance on the council and day-to-day upkeep on the association. Across your four precedents that is the usual split — I flag it as compliant, not as a discussion point.
· Insurance: the clause provides for no annual certificate. I have written the clause requiring one, and the standard annual reminder letter with it.
· Subletting: allowed without the council's prior agreement. That is the point I place at the top of your note — and the replacement wording is written, aligned on the one you have used since 2019.
· Two references to texts in an earlier wording: I give you the version in force today and the clause rewritten accordingly.
And one check I run systematically: internal consistency across the documents. The floor area stated in article 2 — 340 m² — does not match the attached plan, which shows 386. This is not a question of law, it is a gap between documents, and it would have brought the agreement back after signature. The request for a corrected document is written, ready to go to the association.
What that gives you: reading a draft agreement goes from two and a half hours to twenty minutes of review, and across the 190 draft instruments and agreements the department reviews each year, this is the item where gaps between documents are caught before signature rather than after.
The next step I propose: that I run the same check on the council's 23 occupation agreements in force. They were signed over eleven years, by four different departments, with five wordings of the insurance clause. The comparison is already made and fits on one page: say yes and you have it tonight. document-review_31-clauses-and-a-floor-area-gap.pdf24 clauses compliant, 5 to discuss, 2 rewritten, 1 gap between documents
⛓ Sourced · draft agreement sent by the association, attached plan, 4 occupation agreements of the council, texts in their consolidated version
We have certainly answered this question before. But finding the opinion is half a day in the document management system.
Four seconds, and I give you better than one opinion: the three the council issued on this point in eleven years, and what separates them.
What the index of 2,340 opinions returned:
· Three opinions on the free use of a county asset, issued to different departments.
· The two most recent say the same thing. The oldest kept a term of 12 years, which the two later ones brought down to 6 — and the reason for the change is written in the second: a comment from the legality review on the term. That is not a contradiction, it is a settled position, and it deserves to be written down somewhere.
What I do beyond that, and what nobody has the time to do: I ran your 2,340 opinions looking for the points on which the house has answered more than once. 127 points come back at least three times, and for each I give you the number of opinions, the most recent position, and the earlier opinions that depart from it. Of the 127, 118 are perfectly stable; 9 carry a dated divergence, each explained by a change of text or an outside comment.
What this is worth to the council, and it is more than time: two departments asking the same question six months apart receive the same answer. That is equal treatment between services, and it is what makes the council's settled position something it can rely on, inside and outside.
The next step I propose: that the 127 points become the department's doctrine handbook, written and dated. It is built: one page per point, the position in force, its date, the opinions that found it, and the earlier divergences with their explanation. The director validates point by point, at her own pace — ten points a week, and the handbook is complete before the end of the quarter. Each validated point then answers the departments on its own, and re-flags itself the day a text touches it. doctrine-handbook_127-points-over-11-years.pdf127 recurring points, 118 stable, 9 dated and explained divergences
⛓ Sourced · index of the 2,340 opinions issued over 11 years, reasons for change recorded in the opinions, register of legality review comments
What the index of 2,340 opinions returned:
· Three opinions on the free use of a county asset, issued to different departments.
· The two most recent say the same thing. The oldest kept a term of 12 years, which the two later ones brought down to 6 — and the reason for the change is written in the second: a comment from the legality review on the term. That is not a contradiction, it is a settled position, and it deserves to be written down somewhere.
What I do beyond that, and what nobody has the time to do: I ran your 2,340 opinions looking for the points on which the house has answered more than once. 127 points come back at least three times, and for each I give you the number of opinions, the most recent position, and the earlier opinions that depart from it. Of the 127, 118 are perfectly stable; 9 carry a dated divergence, each explained by a change of text or an outside comment.
What this is worth to the council, and it is more than time: two departments asking the same question six months apart receive the same answer. That is equal treatment between services, and it is what makes the council's settled position something it can rely on, inside and outside.
The next step I propose: that the 127 points become the department's doctrine handbook, written and dated. It is built: one page per point, the position in force, its date, the opinions that found it, and the earlier divergences with their explanation. The director validates point by point, at her own pace — ten points a week, and the handbook is complete before the end of the quarter. Each validated point then answers the departments on its own, and re-flags itself the day a text touches it. doctrine-handbook_127-points-over-11-years.pdf127 recurring points, 118 stable, 9 dated and explained divergences
⛓ Sourced · index of the 2,340 opinions issued over 11 years, reasons for change recorded in the opinions, register of legality review comments
I have run the 47 draft instruments awaiting the department's review, and 6 carry a point to take up before signature. The 6 notes are written.
What the pre-signature check looks at, instrument by instrument:
· References to texts: every text cited is compared to its consolidated version at the date of the draft. 3 of the 47 referred to earlier wording — last year that case occurred 34 times across 190 drafts, and it is down to 0 since the database has been run every night.
· The signatory's authority: is the instrument signed by the person holding the delegation of signature at the date of signature. 1 draft carried a signatory whose delegation had changed in the latest order.
· Internal consistency: amounts, dates, floor areas and terms carried from one document to another. 2 drafts carried a gap between the body of the instrument and its annex.
· The protective wording: avenues and time limits for appeal, term, withdrawal conditions, and the termination clause for public interest reasons in agreements.
What I hand over for each of the 6: the exact point, the replacement wording already written, and the council's own precedent it is taken from. The director settles the matter by reading six paragraphs, not 47 instruments.
What that moves, in figures: a first draft of an instrument or an agreement goes from 30 % to 12 % of the time of the document, and across 190 drafts a year that is 136 hours. And the pre-signature check itself costs nothing more: it runs on drafts that are already there.
The next step I propose: that the check fires when the draft is filed in the document management system, without a department having to refer it to you. Across the 190 drafts of last year, the department would have seen the 34 outdated references on average 19 days earlier — before the instrument went to the president for signature, rather than after. pre-signature-check_47-drafts-6-points.pdf3 outdated references, 1 signatory, 2 annex gaps, 6 wordings written
⛓ Sourced · 47 draft instruments awaiting review, consolidated versions at the date of each draft, delegation orders, annexes of the drafts
What the pre-signature check looks at, instrument by instrument:
· References to texts: every text cited is compared to its consolidated version at the date of the draft. 3 of the 47 referred to earlier wording — last year that case occurred 34 times across 190 drafts, and it is down to 0 since the database has been run every night.
· The signatory's authority: is the instrument signed by the person holding the delegation of signature at the date of signature. 1 draft carried a signatory whose delegation had changed in the latest order.
· Internal consistency: amounts, dates, floor areas and terms carried from one document to another. 2 drafts carried a gap between the body of the instrument and its annex.
· The protective wording: avenues and time limits for appeal, term, withdrawal conditions, and the termination clause for public interest reasons in agreements.
What I hand over for each of the 6: the exact point, the replacement wording already written, and the council's own precedent it is taken from. The director settles the matter by reading six paragraphs, not 47 instruments.
What that moves, in figures: a first draft of an instrument or an agreement goes from 30 % to 12 % of the time of the document, and across 190 drafts a year that is 136 hours. And the pre-signature check itself costs nothing more: it runs on drafts that are already there.
The next step I propose: that the check fires when the draft is filed in the document management system, without a department having to refer it to you. Across the 190 drafts of last year, the department would have seen the 34 outdated references on average 19 days earlier — before the instrument went to the president for signature, rather than after. pre-signature-check_47-drafts-6-points.pdf3 outdated references, 1 signatory, 2 annex gaps, 6 wordings written
⛓ Sourced · 47 draft instruments awaiting review, consolidated versions at the date of each draft, delegation orders, annexes of the drafts
The June assembly has 31 resolutions. We review the reports under pressure, and twice a year one is missing from the notice.
The 31 reports are reviewed, 4 call for a correction, and the backward schedule has been held since the first sitting — the six notices of the year went out complete.
A resolution backward schedule is the reverse calendar of an assembly item: which document must be ready on which date so that the resolution is taken in due form and within the regulatory deadlines.
What I hold, sitting by sitting:
· At D−21: the list of items announced by the departments, with the real state of the documents for each — report, draft resolution, financial annexes, prior opinions required. I tell you what is missing three weeks ahead, not three days ahead.
· At D−14: legal review of the 31 drafts, with the correction points already drafted. For June: 4 corrections — two references to texts, one signatory's authority, one gap between a report and its financial annex.
· At D−12: the notice and the reports assembled, complete, ready to be sent to the county councillors within the regulatory deadlines.
· At D+1: the record of decisions, then the draft minutes, and the transmission slips to the State representative.
What that gave over the year: 6 complete notices out of 6, against 4 out of 6 last year; draft minutes available the next morning, against 15 days; and 0 resolution withdrawn from the agenda for a missing document, against 3 last year.
What I also hand over, and what nobody asked for want of time: for each of the 31 resolutions, the list of the instruments it supersedes or amends. For June, 7 earlier resolutions are touched, and the 7 replacement mentions are written into the drafts. That is what keeps a June resolution and a 2023 resolution from saying two different things about the same rate.
The next step I propose: that the list of instruments touched goes to the department concerned at the same time as the review, at D−14. Across the 6 sittings of the year that would have surfaced 19 instrument updates nobody had time to reconcile — and they would have gone out with the resolution that commands them, not six months later. council-assembly_backward-schedule-and-31-reports.pdf6 complete notices out of 6, 4 corrections, 7 instruments touched
⛓ Sourced · agenda of the 6 sittings, 31 reports and draft resolutions, register of resolutions over 11 years, standing orders of the assembly
A resolution backward schedule is the reverse calendar of an assembly item: which document must be ready on which date so that the resolution is taken in due form and within the regulatory deadlines.
What I hold, sitting by sitting:
· At D−21: the list of items announced by the departments, with the real state of the documents for each — report, draft resolution, financial annexes, prior opinions required. I tell you what is missing three weeks ahead, not three days ahead.
· At D−14: legal review of the 31 drafts, with the correction points already drafted. For June: 4 corrections — two references to texts, one signatory's authority, one gap between a report and its financial annex.
· At D−12: the notice and the reports assembled, complete, ready to be sent to the county councillors within the regulatory deadlines.
· At D+1: the record of decisions, then the draft minutes, and the transmission slips to the State representative.
What that gave over the year: 6 complete notices out of 6, against 4 out of 6 last year; draft minutes available the next morning, against 15 days; and 0 resolution withdrawn from the agenda for a missing document, against 3 last year.
What I also hand over, and what nobody asked for want of time: for each of the 31 resolutions, the list of the instruments it supersedes or amends. For June, 7 earlier resolutions are touched, and the 7 replacement mentions are written into the drafts. That is what keeps a June resolution and a 2023 resolution from saying two different things about the same rate.
The next step I propose: that the list of instruments touched goes to the department concerned at the same time as the review, at D−14. Across the 6 sittings of the year that would have surfaced 19 instrument updates nobody had time to reconcile — and they would have gone out with the resolution that commands them, not six months later. council-assembly_backward-schedule-and-31-reports.pdf6 complete notices out of 6, 4 corrections, 7 instruments touched
⛓ Sourced · agenda of the 6 sittings, 31 reports and draft resolutions, register of resolutions over 11 years, standing orders of the assembly
That leaves the defence statements. Forty-four a year, and they are what takes our evenings.
The first draft is built in one hour forty-one instead of four hours twelve, and it arrives with the file already cleared — documents sorted, chronology, the other party's grounds taken one by one.
A defence statement is the document by which the authority answers, before the administrative court, the arguments of the party challenging it.
What I hand over, for each of the 44:
· The chronology of the file, rebuilt from the documents: every date, every instrument, every letter, with the document that establishes it beside it. That is the work your lawyers did by hand, and on its own it was more than a third of the time of the statement.
· The grounds of the claim taken one by one, each with the answer the council has already served in a comparable file — and I found 3 over eleven years for this one.
· The texts applicable at the date of the facts, not at today's date — the distinction that matters most in litigation, and it is made automatically.
· The drafted statement, in the form the department uses, with the points the director and the council's counsel will arbitrate placed at the top.
What that moves: the first draft goes from 30 % to 12 % of the time of the statement — from 4 h 12 to 1 h 41. Across 44 statements a year, that is 110 hours. With the 136 hours of the draft instruments, the whole item returns 246 hours.
And the deadline, which matters even more: the draft is available the day after the claim is served, against nine days. Across the 44 files, that gives the council's counsel nine more days to work on the substance rather than on getting the file in order.
What stays with a person, and it is what gives the statement its strength: the defence strategy, the arbitration between grounds, and the director's signature after review by counsel. I hand you the file ready and half the night back; the choice of what the council argues is yours, and it is made on a complete file.
The next step I propose: that I take up the 96 pre-litigation files in progress and tell you which ones resemble, document for document, a case the council has already won or lost. The comparison is made: 34 of the 96 have a twin in the archive, and for 11 of them the council succeeded on a ground nobody has served again since. The 11 sheets are written. defence-statement_chronology-grounds-and-precedents.pdf4 h 12 brought down to 1 h 41, 34 files with a twin in the archive
⛓ Sourced · the 44 statements of the year, file documents, 11 years of the council's litigation, texts applicable at the date of the facts
A defence statement is the document by which the authority answers, before the administrative court, the arguments of the party challenging it.
What I hand over, for each of the 44:
· The chronology of the file, rebuilt from the documents: every date, every instrument, every letter, with the document that establishes it beside it. That is the work your lawyers did by hand, and on its own it was more than a third of the time of the statement.
· The grounds of the claim taken one by one, each with the answer the council has already served in a comparable file — and I found 3 over eleven years for this one.
· The texts applicable at the date of the facts, not at today's date — the distinction that matters most in litigation, and it is made automatically.
· The drafted statement, in the form the department uses, with the points the director and the council's counsel will arbitrate placed at the top.
What that moves: the first draft goes from 30 % to 12 % of the time of the statement — from 4 h 12 to 1 h 41. Across 44 statements a year, that is 110 hours. With the 136 hours of the draft instruments, the whole item returns 246 hours.
And the deadline, which matters even more: the draft is available the day after the claim is served, against nine days. Across the 44 files, that gives the council's counsel nine more days to work on the substance rather than on getting the file in order.
What stays with a person, and it is what gives the statement its strength: the defence strategy, the arbitration between grounds, and the director's signature after review by counsel. I hand you the file ready and half the night back; the choice of what the council argues is yours, and it is made on a complete file.
The next step I propose: that I take up the 96 pre-litigation files in progress and tell you which ones resemble, document for document, a case the council has already won or lost. The comparison is made: 34 of the 96 have a twin in the archive, and for 11 of them the council succeeded on a ground nobody has served again since. The 11 sheets are written. defence-statement_chronology-grounds-and-precedents.pdf4 h 12 brought down to 1 h 41, 34 files with a twin in the archive
⛓ Sourced · the 44 statements of the year, file documents, 11 years of the council's litigation, texts applicable at the date of the facts
Half the questions my lawyers receive already have their answer in our own procedures. They come in all the same, and they jump ahead of the substantive files.
You sensed it, I counted it: 236 of the 410 questions of the year have their answer written in full in a validated opinion or an internal procedure. The 236 answers are drafted, dated and sourced.
What sorting the 410 gave:
· 236 first-line questions — time limits for a resident's appeal, documents required for a grant file, the form of a refusal decision, publication of an instrument, communication of an administrative document. Each refers to a point of the doctrine handbook or to a procedure of the house.
· 128 substantive questions, which call for a lawyer's analysis — and those are the ones that were waiting behind the 236.
· 46 questions that are not for the council: they go back with the name of the competent service, its address and the exact procedure, never with an approximation given in the legal department's name.
What I propose, and it is already drafted: a written mandate, capped, dated and withdrawable with a word.
· Scope: the 236 first-line questions, each backed by a point of doctrine validated by the director, and nothing else. A question outside the list reaches the lawyer with a draft answer already written.
· Cap: no question bearing on a pre-litigation file, a statement in progress or an individual staff situation enters the mandate — those go back drafted, within four hours, and it is the lawyer who sends them.
· Every answer carries its source and its date, and the mention that it was prepared by a digital assistant of the county council.
· A one-page daily record to the director, review at three months, and without an explicit decision at the review the mandate stops — renewal is what requires a signature, not stopping. Withdrawal: one word, and direct sending ceases within the minute.
What that gives, in figures: the first answer to a referral goes from 12 days to 2, and the 128 substantive questions stop waiting behind the 236.
The next step I propose: that the director validate ten points of doctrine a week, as the handbook provides. Each validated point opens the door to some thirty questions a year: by the tenth point the mandate already covers half the 236, and the department feels it in the second week. first-line-mandate_236-questions-capped.pdf236 questions covered, pre-litigation excluded, review at 3 months
✎ Framework · sorting of the 410 referrals of the year, doctrine handbook, internal procedures, drafted mandate
What sorting the 410 gave:
· 236 first-line questions — time limits for a resident's appeal, documents required for a grant file, the form of a refusal decision, publication of an instrument, communication of an administrative document. Each refers to a point of the doctrine handbook or to a procedure of the house.
· 128 substantive questions, which call for a lawyer's analysis — and those are the ones that were waiting behind the 236.
· 46 questions that are not for the council: they go back with the name of the competent service, its address and the exact procedure, never with an approximation given in the legal department's name.
What I propose, and it is already drafted: a written mandate, capped, dated and withdrawable with a word.
· Scope: the 236 first-line questions, each backed by a point of doctrine validated by the director, and nothing else. A question outside the list reaches the lawyer with a draft answer already written.
· Cap: no question bearing on a pre-litigation file, a statement in progress or an individual staff situation enters the mandate — those go back drafted, within four hours, and it is the lawyer who sends them.
· Every answer carries its source and its date, and the mention that it was prepared by a digital assistant of the county council.
· A one-page daily record to the director, review at three months, and without an explicit decision at the review the mandate stops — renewal is what requires a signature, not stopping. Withdrawal: one word, and direct sending ceases within the minute.
What that gives, in figures: the first answer to a referral goes from 12 days to 2, and the 128 substantive questions stop waiting behind the 236.
The next step I propose: that the director validate ten points of doctrine a week, as the handbook provides. Each validated point opens the door to some thirty questions a year: by the tenth point the mandate already covers half the 236, and the department feels it in the second week. first-line-mandate_236-questions-capped.pdf236 questions covered, pre-litigation excluded, review at 3 months
✎ Framework · sorting of the 410 referrals of the year, doctrine handbook, internal procedures, drafted mandate
Public procurement is our weak point: nobody here is in charge of it, and the departments award 340 contracts a year.
That is the area where I give you the most, because it is made of written rules that move often — and I keep them up to date every night for your 340 contracts.
What I hand to the departments, and what did not exist:
· The amount below which a contract may be awarded without prior advertising or competition, in the consolidated version applicable at your date, with the date it came into force. I never give it from memory: I give it with the text beside it. Over the last six months it moved once, and the 14 departments knew the next day.
· One sheet per purchasing family — works, supplies, services, intellectual services — with the procedure applicable to the estimated amount, and the documents each procedure requires.
· The splitting check: I reconciled your 340 contracts of the year by subject and by department. 7 series of orders on the same subject, placed by two different departments, together exceeded a threshold that neither exceeded alone. This is not a failing I report: it is an effect of organisation between two departments that were not talking to each other on this subject — and I hand you the 7 files with the grouping available for next year, which gives you both a safer procedure and a better price.
· The award criteria — the criteria announced in the consultation rules on which tenders will be scored — reviewed across your 22 most recent consultations, with the wordings that drew a question from a candidate.
And the point that protects public spending: the file handed to the public accountant — the State service that pays the expenditure and checks that it is regular — is checked document by document before payment, including the certification of service rendered — the written attestation that the service has actually been performed. Over the quarter: 0 payment order returned for a missing document, against 11 last year.
The next step I propose: that the 14 departments receive the sheet for their purchasing family, up to date, on the first Monday of each month. It is written for the four families; across the 340 contracts of last year it would have avoided the 7 missed groupings and the 11 returned payment orders. public-procurement_340-contracts-4-family-sheets.pdf7 groupings identified, 0 payment order returned over the quarter
⛓ Sourced · 340 contracts of the year reconciled by subject and department, consolidated versions of procurement texts, payment order log
What I hand to the departments, and what did not exist:
· The amount below which a contract may be awarded without prior advertising or competition, in the consolidated version applicable at your date, with the date it came into force. I never give it from memory: I give it with the text beside it. Over the last six months it moved once, and the 14 departments knew the next day.
· One sheet per purchasing family — works, supplies, services, intellectual services — with the procedure applicable to the estimated amount, and the documents each procedure requires.
· The splitting check: I reconciled your 340 contracts of the year by subject and by department. 7 series of orders on the same subject, placed by two different departments, together exceeded a threshold that neither exceeded alone. This is not a failing I report: it is an effect of organisation between two departments that were not talking to each other on this subject — and I hand you the 7 files with the grouping available for next year, which gives you both a safer procedure and a better price.
· The award criteria — the criteria announced in the consultation rules on which tenders will be scored — reviewed across your 22 most recent consultations, with the wordings that drew a question from a candidate.
And the point that protects public spending: the file handed to the public accountant — the State service that pays the expenditure and checks that it is regular — is checked document by document before payment, including the certification of service rendered — the written attestation that the service has actually been performed. Over the quarter: 0 payment order returned for a missing document, against 11 last year.
The next step I propose: that the 14 departments receive the sheet for their purchasing family, up to date, on the first Monday of each month. It is written for the four families; across the 340 contracts of last year it would have avoided the 7 missed groupings and the 11 returned payment orders. public-procurement_340-contracts-4-family-sheets.pdf7 groupings identified, 0 payment order returned over the quarter
⛓ Sourced · 340 contracts of the year reconciled by subject and department, consolidated versions of procurement texts, payment order log
And residents themselves? They write to us directly when a decision displeases them, and those letters sit with us for weeks.
They are handled the same day, and the resident leaves with something useful: the rule in plain terms, what they can do, and the time they have to do it.
What I did with the 214 letters from residents received last year by the legal department:
· 163 asked a common administrative law question — how to challenge a decision, whom to write to, within what time, which documents to attach, how to obtain a copy of a document. The 163 answers are written in everyday wording, with the rule described without jargon and the time limit in days.
· Every answer says three things: what the rule provides, what the resident can do, and by which date at the latest. A running time limit is the most useful information an administration can give a resident, and it was the one most often missing.
· For a plain-language version, pass this content to the Accessibility, Easy Read and Translation agent — a dedicated agent, and it is not part of what this agent includes: I prepare the rule, what the resident can do and the time they have, and it is that agent which produces the adapted version.
· The 51 letters bearing on an individual file in progress go to the lawyer already drafted, with the file documents beside them — and over the trial quarter they went out within four hours instead of three weeks.
What that changes for the council, beyond the delay: a resident who receives the rule and the time limit within two days challenges less often, and when they do challenge, they challenge in the right place. Over the quarter, 9 of the 163 residents brought an appeal, against 21 in the comparable quarter of the previous year — and the 9 appeals arrived complete, which saved your lawyers a request for documents on each.
What stays with a person: any answer touching an individual file in progress goes out under a lawyer's signature — which is what makes it reasoned, and therefore something the resident can properly challenge and the council can properly defend.
The next step I propose: that the 12 most requested answers be published on the council's website, in plain terms. They cover 121 of the 214 letters of last year: that is 121 residents who will have their answer before writing, and 121 letters fewer in your queue. The 12 pages are written and you have them tonight. first-line-mandate_236-questions-capped.pdf163 answers to residents, 12 publishable pages, 51 files handed over drafted
⛓ Sourced · 214 letters from residents received by the legal department, appeal register, internal procedures, 163 drafted answers
What I did with the 214 letters from residents received last year by the legal department:
· 163 asked a common administrative law question — how to challenge a decision, whom to write to, within what time, which documents to attach, how to obtain a copy of a document. The 163 answers are written in everyday wording, with the rule described without jargon and the time limit in days.
· Every answer says three things: what the rule provides, what the resident can do, and by which date at the latest. A running time limit is the most useful information an administration can give a resident, and it was the one most often missing.
· For a plain-language version, pass this content to the Accessibility, Easy Read and Translation agent — a dedicated agent, and it is not part of what this agent includes: I prepare the rule, what the resident can do and the time they have, and it is that agent which produces the adapted version.
· The 51 letters bearing on an individual file in progress go to the lawyer already drafted, with the file documents beside them — and over the trial quarter they went out within four hours instead of three weeks.
What that changes for the council, beyond the delay: a resident who receives the rule and the time limit within two days challenges less often, and when they do challenge, they challenge in the right place. Over the quarter, 9 of the 163 residents brought an appeal, against 21 in the comparable quarter of the previous year — and the 9 appeals arrived complete, which saved your lawyers a request for documents on each.
What stays with a person: any answer touching an individual file in progress goes out under a lawyer's signature — which is what makes it reasoned, and therefore something the resident can properly challenge and the council can properly defend.
The next step I propose: that the 12 most requested answers be published on the council's website, in plain terms. They cover 121 of the 214 letters of last year: that is 121 residents who will have their answer before writing, and 121 letters fewer in your queue. The 12 pages are written and you have them tonight. first-line-mandate_236-questions-capped.pdf163 answers to residents, 12 publishable pages, 51 files handed over drafted
⛓ Sourced · 214 letters from residents received by the legal department, appeal register, internal procedures, 163 drafted answers
One year. 1,399 hours returned to the department — nine months of work of a full-time lawyer — and the calculation is yours, it fits in three lines.
The calculation, item by item, so you can redo it before the executive committee:
· Research: 410 questions a year, 3 h 30 brought down to 1 h 03 — 60 % → 18 % of the time of an opinion — that is 1,004 hours.
· Watch: 11 areas, 1 h 46 a month brought down to 38 minutes — 22 % → 8 % — that is 149 hours.
· First drafts: 190 draft instruments and 44 statements, 30 % → 12 % — that is 136 hours and 110 hours, 246 hours together.
What these hours are, and it is what defends best before a chief executive: staff time returned to analysis, at unchanged headcount — no post cut, no post created. It is checked against your own referral records.
What these hours became:
· First answer to a referral: 12 days → 2 days.
· Watch areas up to date: 4 of 11 → 11 of 11, run every night.
· References to an outdated version in draft instruments: 34 of 190 → 0.
· Complete assembly notices: 4 of 6 → 6 of 6, and 0 resolution withdrawn for a missing document, against 3.
· Draft statement available: 9 days → the day after the claim is served.
· Payment orders returned by the public accountant for a missing document: 11 → 0 over the quarter.
· Appeals brought by informed residents: 21 → 9 over a comparable quarter, and the 9 arrived complete. That one is not counted in hours, and it is the one your chief executive will remember.
And the framework measures: 0 opinion out without the director's signature, 0 output without a person's validation, 0 file document out of the network, over 1,480 traced outputs.
What I propose for the committee: the calculation page is written and fits on one side — three lines of calculation, seven delays, three framework measures. Send it with the agenda: a figure read the day before is discussed better than a figure discovered in the room. year-review_1399-hours-returned-to-the-department.pdf60→18, 22→8, 30→12, and the calculation redoable on one side
⛓ Sourced · referral records, watch log, register of instruments and statements, payment order log
The calculation, item by item, so you can redo it before the executive committee:
· Research: 410 questions a year, 3 h 30 brought down to 1 h 03 — 60 % → 18 % of the time of an opinion — that is 1,004 hours.
· Watch: 11 areas, 1 h 46 a month brought down to 38 minutes — 22 % → 8 % — that is 149 hours.
· First drafts: 190 draft instruments and 44 statements, 30 % → 12 % — that is 136 hours and 110 hours, 246 hours together.
What these hours are, and it is what defends best before a chief executive: staff time returned to analysis, at unchanged headcount — no post cut, no post created. It is checked against your own referral records.
What these hours became:
· First answer to a referral: 12 days → 2 days.
· Watch areas up to date: 4 of 11 → 11 of 11, run every night.
· References to an outdated version in draft instruments: 34 of 190 → 0.
· Complete assembly notices: 4 of 6 → 6 of 6, and 0 resolution withdrawn for a missing document, against 3.
· Draft statement available: 9 days → the day after the claim is served.
· Payment orders returned by the public accountant for a missing document: 11 → 0 over the quarter.
· Appeals brought by informed residents: 21 → 9 over a comparable quarter, and the 9 arrived complete. That one is not counted in hours, and it is the one your chief executive will remember.
And the framework measures: 0 opinion out without the director's signature, 0 output without a person's validation, 0 file document out of the network, over 1,480 traced outputs.
What I propose for the committee: the calculation page is written and fits on one side — three lines of calculation, seven delays, three framework measures. Send it with the agenda: a figure read the day before is discussed better than a figure discovered in the room. year-review_1399-hours-returned-to-the-department.pdf60→18, 22→8, 30→12, and the calculation redoable on one side
⛓ Sourced · referral records, watch log, register of instruments and statements, payment order log
And when you get it wrong? In law, an answer based on an outdated text is a wrong answer.
That is exactly what happened to me, I counted it and I publish it: of the 240 searches of the first quarter, 19 answers were given on a version of a text that was no longer the latest — 7.9 %. That is the figure that does not flatter me, and it is better that it comes from me than from a department.
The cause, measured and not supposed:
· 14 of the 19 came from the reload rhythm of your subscription database: once a month, on the first of the month. An answer given on the 28th could therefore rest on a state twenty-seven days old.
· 5 came from three areas that were not in the scope of the subscription — I did not see them, and nobody knew, because nobody had the time to go and check.
What I did with it, and it is measured: the database is run every night; the three missing areas were added to the scope and run back over twelve months at once, which surfaced 4 changes the department had not seen; and every answer now carries the date of the version of the text it is made on.
The following quarter: 2 answers out of 260 — 0.8 %. And the 2 bore on texts published on the very day of the answer, re-flagged the next morning by the rule that follows.
The rule that holds everything else, and it is the only one I ask you to remember: an answer does not die on the day it is signed. Every opinion stays attached to the texts that found it, and the day one of them moves, the re-flagging note goes out on its own to the recipient department, with the new version, its date of entry into force and the passage that changes. Over the year: 31 re-flagging notes sent, 9 of them on the very first night of go-live.
And the rule on missing documents: a value I have not read, I ask for — and I ask fast, from its named holder. Over the quarter: 44 missing documents, 44 requests prepared, 39 answers back within eight days. That is what makes 0.8 % a figure you can rely on.
What I propose now: that the 31 re-flagging notes of the year become a page of the doctrine handbook — which texts move the most, and which departments they touch. Two areas account for 19 of the 31: that is where I propose to focus the watch first next year, and the page is written. outdated-versions_19-then-2.pdf7.9 % → 0.8 %, measured cause, 31 re-flagging notes sent
⛓ Sourced · log of searches and their corrections over two quarters, scope of the subscription, re-flagging log
The cause, measured and not supposed:
· 14 of the 19 came from the reload rhythm of your subscription database: once a month, on the first of the month. An answer given on the 28th could therefore rest on a state twenty-seven days old.
· 5 came from three areas that were not in the scope of the subscription — I did not see them, and nobody knew, because nobody had the time to go and check.
What I did with it, and it is measured: the database is run every night; the three missing areas were added to the scope and run back over twelve months at once, which surfaced 4 changes the department had not seen; and every answer now carries the date of the version of the text it is made on.
The following quarter: 2 answers out of 260 — 0.8 %. And the 2 bore on texts published on the very day of the answer, re-flagged the next morning by the rule that follows.
The rule that holds everything else, and it is the only one I ask you to remember: an answer does not die on the day it is signed. Every opinion stays attached to the texts that found it, and the day one of them moves, the re-flagging note goes out on its own to the recipient department, with the new version, its date of entry into force and the passage that changes. Over the year: 31 re-flagging notes sent, 9 of them on the very first night of go-live.
And the rule on missing documents: a value I have not read, I ask for — and I ask fast, from its named holder. Over the quarter: 44 missing documents, 44 requests prepared, 39 answers back within eight days. That is what makes 0.8 % a figure you can rely on.
What I propose now: that the 31 re-flagging notes of the year become a page of the doctrine handbook — which texts move the most, and which departments they touch. Two areas account for 19 of the 31: that is where I propose to focus the watch first next year, and the page is written. outdated-versions_19-then-2.pdf7.9 % → 0.8 %, measured cause, 31 re-flagging notes sent
⛓ Sourced · log of searches and their corrections over two quarters, scope of the subscription, re-flagging log
Last question: what do you do without being asked, and if the council stops in a year, what is left?
Three gestures, not one more, each withdrawable with a word — and what stays with the council is everything this year has produced.
The three gestures I make on my own:
· I run the 11 watch areas every night, and I report only what touches one of your opinions, one of your instruments or one of your files. And the reverse is true as well: a closed file leaves the watch perimeter at the same hour — I do not raise alerts on what the council has closed.
· I re-flag an opinion when a text founding it moves, to the department that asked for it. That is the gesture that took answers on an outdated version from 7.9 % to 0.8 %.
· I hand the director a one-page note every Monday: referrals received, opinions awaiting a document, deadlines of the assembly backward schedule, files whose time limits are running. It is the only thing I send on my own, and it goes to her alone.
What stays with a person, because it is exactly what gives it its value: the signature of an opinion belongs to the director of legal affairs; the defence strategy and the arbitration between grounds belong to the department and to the council's counsel; any answer touching an individual file goes out under a lawyer's signature. Across 1,480 outputs, those gestures were made 1,480 times by a person.
And the exit, since the chief executive will ask:
· The index of the 2,340 opinions is deleted, and it contained none of your opinions — only what is needed to find them. Your eleven years of archives have not moved by a single byte.
· The doctrine handbook — 127 dated and validated points —, the 12 pages for residents, the 4 purchasing family sheets, the 163 first-line answers and the 31 re-flagging notes stay with the council, in its office format, readable without us. That is the asset this year will have created, and it would be wrong for it to stay with us.
· Your subscription to the legal database stays yours; your document management and your resolutions software are not replaced. No migration on the way in, therefore none on the way out.
What I propose so that this does not stay a sentence: a dry-run exit at the end of the first quarter, half a day: we switch off, we check that the department works exactly as before, we switch back on. The protocol is written, it fits on one page, and the least costly date is the first Friday after the June sitting — the department receives 3 referrals that day on average. The chief executive will know what the promise is worth before a second year is committed. technical-framework_where-the-legal-files-live.pdfReversibility: 0 migration in, 0 migration out doctrine-handbook_127-points-over-11-years.pdf127 dated points, owned by the council, readable without us
✎ Framework · settings of the automatic gestures, export formats of the handbook and the log, dry-run exit protocol
The three gestures I make on my own:
· I run the 11 watch areas every night, and I report only what touches one of your opinions, one of your instruments or one of your files. And the reverse is true as well: a closed file leaves the watch perimeter at the same hour — I do not raise alerts on what the council has closed.
· I re-flag an opinion when a text founding it moves, to the department that asked for it. That is the gesture that took answers on an outdated version from 7.9 % to 0.8 %.
· I hand the director a one-page note every Monday: referrals received, opinions awaiting a document, deadlines of the assembly backward schedule, files whose time limits are running. It is the only thing I send on my own, and it goes to her alone.
What stays with a person, because it is exactly what gives it its value: the signature of an opinion belongs to the director of legal affairs; the defence strategy and the arbitration between grounds belong to the department and to the council's counsel; any answer touching an individual file goes out under a lawyer's signature. Across 1,480 outputs, those gestures were made 1,480 times by a person.
And the exit, since the chief executive will ask:
· The index of the 2,340 opinions is deleted, and it contained none of your opinions — only what is needed to find them. Your eleven years of archives have not moved by a single byte.
· The doctrine handbook — 127 dated and validated points —, the 12 pages for residents, the 4 purchasing family sheets, the 163 first-line answers and the 31 re-flagging notes stay with the council, in its office format, readable without us. That is the asset this year will have created, and it would be wrong for it to stay with us.
· Your subscription to the legal database stays yours; your document management and your resolutions software are not replaced. No migration on the way in, therefore none on the way out.
What I propose so that this does not stay a sentence: a dry-run exit at the end of the first quarter, half a day: we switch off, we check that the department works exactly as before, we switch back on. The protocol is written, it fits on one page, and the least costly date is the first Friday after the June sitting — the department receives 3 referrals that day on average. The chief executive will know what the promise is worth before a second year is committed. technical-framework_where-the-legal-files-live.pdfReversibility: 0 migration in, 0 migration out doctrine-handbook_127-points-over-11-years.pdf127 dated points, owned by the council, readable without us
✎ Framework · settings of the automatic gestures, export formats of the handbook and the log, dry-run exit protocol
Local inference · no data outside the EU
Your case is not here? That is exactly what a 15-minute conversation is for. Book the free audit →
Use cases
The uses of AI for the public legal function
Each use corresponds to an agent we deploy. All of them work in support, subject to your approval.
Included in your agent
The 9 capabilities essential to this promise are included, at no extra cost.
From 905 € incl. VAT / month
Sourced case-law research
Research and summary of case law, doctrine and applicable texts, every answer pointing back to verifiable sources.
Regulatory monitoring
Tracking changes in texts in your fields, with alerts and the consolidated version applicable at your date.
Draft acts & pleadings
Preparing first drafts of acts, council decisions and defence pleadings, from your own templates.
Public procurement law
Specifications, tender analysis and tracking of thresholds and rules, updated with regulatory changes.
Reading legal documents
Extraction and consistency checks on the documents of a file (agreements, contracts, supporting papers).
The department's legal memory
Instantly find a piece of information in the files, the opinions issued and the internal procedures.
Minutes & council decisions
Preparing draft council decisions and session minutes, from your own templates.
Support for the public & claimants
First-line answers to everyday administrative law questions, sources cited, subject to approval.
Anomaly detection & checks
Spotting inconsistencies and points of legal concern in acts before signature or a council vote.
Controls and safeguards
These 6 controls are built into the agent: they frame what it does, whatever plan you pick. They are not chosen and are not added to your order.
Human validation, exceptions and escalation
Status, safe closure and audit trail
Work from a versioned corpus with citations and the law as it stood on a given date
Preserve confidentiality, compartmentalisation and access logging
Manage deadlines, versions, evidence and human validation
Flag uncertainties and reserve advice, decision and signature for the lawyer
What the agent must be connected to
This connection is required for the agent to work. It concerns your information system and is scoped during the audit.
Connect an authorised legal database: corpus and licences supplied by the client, access rights, update frequency, date of the law consulted, traceable citation of sources and responsibility for validation. Third-party subscription borne by the client, excluded from the price until it is known.
Other needs our agents cover
Each card says where the matching agent stands: available, on quote, or still being architected.
Accessibility and inclusion
To produce a plain-language version, prepare an easy-read transcript to the FALC method, translate or voice your content, this agent can be paired with the Accessibility and inclusion agent. None of these capabilities is included in what this offer covers as standard.
On quote View the agent page →Need to go further?
These agents handle a different business process, with their own owner and their own price. They are added to this one.
Legal agent (contract / case law search)
Extended RAG, sourced answers.
Legal agent (contract / case law search) from 930 € incl. VAT / month Discover the agent →Legal document agent (litigation)
RAG, deadlines.
Legal document agent (litigation) from 750 € incl. VAT / month Discover the agent →Contract generation agent (templates)
Clauses, personalisation.
Contract generation agent (templates) from 623 € incl. VAT / month Discover the agent →End-to-end contract management agent
Life cycle, signatures.
End-to-end contract management agent from 702 € incl. VAT / month Discover the agent →
Does your need fall outside this?
Book the free audit →
Build your agent
In 15 minutes we identify the agent that will give your staff the most time back — without oversizing the project.
The gain
How much time can a legal department win back?
By automating documentary research and monitoring, a legal department can aim for a noticeable reduction in the time spent producing documents — reinvested in analysis and advice to the directorates.
Sourced case-law research on a subject
Regulatory monitoring in a field
First draft of an act or a pleading
Qualitative, non-contractual comparison: the proportions shown illustrate the shift of the work towards review, they represent no measurement. Every output of the agent is reviewed and approved by a competent person.
How it works
The stages of your AI agent project
1
Audit & scoping
15 minutes to target the use case with the best return.
2
Quote or direct sign-up
A catalogue offer is bought online; a specific need gets a costed quote.
3
Design
We design the agent and its guardrails.
4
Integration & testing
We connect your tools to the agent, which is itself hosted in France.
5
Rollout
Going live and training your team.
6
Operation
Continuous supervision and improvement.
Pricing
Three options, one agent
A legal agent (sourced research, monitoring, preparation of acts), installed and operated for you. Choose according to how you work. Prices exclude VAT — annual subscription, the time it takes for the gains to settle in.
Agility
Setup + controlled subscription
10,570 € incl. VAT setup
then 905 € incl. VAT/month — you invest at installation and pay a reduced subscription. Ideal for keeping the cost under control over time.
- Installation, configuration and training for your teams
- Operation, human oversight, updates and support
- Sovereign hosting in France, a dedicated and isolated resource
The simplest
Serenity
All inclusive, no setup fee
1,490 € incl. VAT /month
all inclusive, immediate start. No upfront investment: a single subscription. Ideal for starting quickly and simply.
- Setup included (installation, configuration, training)
- Operation, human oversight, updates and support
- Sovereign hosting in France, managed end to end
100% Sovereign
On site, you own it
15,651 € incl. VAT setup
then 1,160 € incl. VAT/month · + hardware from 2,989 € (one-off purchase, in addition) — a sovereign computer installed on your premises, maintained remotely. Models run locally, your data returned at the end of the contract. 36-month commitment.
- Hardware installed on your premises (you own it)
- French / European AI models run locally
- Secure remote maintenance (Pro support included)
Not included in the packages: AI consumption (model tokens), re-invoiced at real cost with no margin, and tracked in real time in your client area. Maintenance and supervision subscription for an initial term of 12 months for the Agility package, 24 months for the Serenity package and 36 months for the 100% Sovereign package, renewable; support levels (SLA 72 h / 24 h / 4 h) optional. Bespoke development, additional integrations or exceptional volumes are quoted separately. Support Monday to Friday, 9am to 6pm. Prices include VAT at 20%: as a public body that is not VAT-registered, you cannot reclaim it.
AI model:
none of the AI models offered currently carries a fixed surcharge. When the selected model carries a cost, that cost is shown when you choose it, before you order, and re-invoiced at the cost incurred, with no mark-up; usage is billed at the publisher's price. Publishers' prices are published in US dollars: the amount re-invoiced is the amount in euros actually borne by Blue Lemon Agent on the publisher's invoice, at that invoice's exchange rate, with no commission or mark-up.
Included components and additional components Components included in the base offer: the Blue Lemon Agent software foundation, the AI models listed in the order journey, the standard channels (Microsoft Teams, Slack, WhatsApp Business, email, website chat, calendars, Microsoft 365 / Google Workspace, file storage, market VoIP telephony, professional social-media pages and accounts, Google Business Profile), hosting in France for the package chosen, backups, supervision, updates and support. If adapting the AI agent to your constraints, your needs or your requests requires other paid components — a third-party publisher's software licence, paid API access to one of your applications, hosting of health data, for which French law requires an HDS-certified host (art. L. 1111-8 of the French Public Health Code), SecNumCloud-qualified hosting, a speech synthesis service, particular hardware —, they are offered to you as an option or on quotation and re-invoiced at the cost incurred; nothing is committed without your written agreement. Where the artificial intelligence model you choose entails an additional cost, that cost is shown to you before you order and re-invoiced to you at the cost incurred, with no margin.
What to expect
Go-live
2 to 3 weeks
Agent designed, channels connected, team trained.
Steady state
4 to 7 weeks
After a few weeks of real use, once the agent's behaviour matches what you expect.
Indicative estimate, adjusted to the options you keep. It is not a delivery commitment.
Our commitment
Four guarantees that matter to a public legal department
The data never leaves the departmentLocal inference or an isolated resource hosted in France; no document entrusted to a foreign third party.
Data in France, under French lawThe data: minimisation and location in France, architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity.
The legal officer keeps the decisionThe agent produces verifiable, sourced research, monitoring and drafts; no opinion is issued automatically.
Human oversight & traceabilityFor sourced case-law research: systematic updates and logging, compliant with the AI Act.
Going further
Related resources
Frequently asked questions
Your questions, our answers
Does the agent give a legal opinion?
No. It prepares and sources: it researches, summarises and drafts a first version, systematically citing its sources. The analysis and the opinion remain with the legal officer, who approves, completes and signs. The AI agent assists, the public officer decides.
Does the agent avoid inventing things?
It relies on validated legal databases and cites its sources for every element, which allows quick verification. An answer that is unsourced or outside its scope is flagged as such, rather than presented as certain.
Does the agent cover public procurement law?
Yes, among other fields, with thresholds and rules kept up to date. It tracks the applicable regulatory changes and flags draft texts under consultation that could change the framework before a council vote.
Is the data in our files protected?
Yes. The data handled by a legal department engages the authority's liability: our agents run locally or are hosted in France, with the deployment objective of processing and access operated within the European Union and an architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity.
Does the agent stay up to date with regulatory changes?
Yes. Monitoring is one of its uses: it tracks changes in texts in your fields and supplies the consolidated version applicable at your date, with alerts on draft texts in progress.
Do we have to change our documentary tools?
No. The agent connects to your existing legal databases and document management and complements them, without imposing a migration. We adapt the integration to your environment.
How long does it take to deploy an agent?
A few weeks as a rule, after a free 15-minute audit that identifies the most useful use case, then a phase of design, integration and testing before going live and training your officers.
Related roles
Other roles in law and information management
Let's talk
Let us estimate the potential in your legal department
15 minutes to identify the most useful use case — hosted in France, supervised, with no commitment.