● Public sector — Prefecture officer
AI agent for the prefecture officer (permits & residence)
An assistant that pre-assesses permit applications, checks the documents and prepares the replies — the state officer keeps the assessment and the decision. Hosted in France — on local inference or an isolated resource — identity and residence data never leaves the country. The AI agent assists, the public officer decides.
Hosted in France
Identity data protected
GDPR & AI Act: governed deployment
The state officer decides
Updated on
Deployed in a few weeks
Prefecture assistant · hosted in France
Check this student residence permit renewal file is complete before assessment.
Check carried out. Eight documents out of nine in order: valid passport, current permit, 2025-2026 enrolment certificate, proof of address less than six months old.
The proof of means is missing — a draft request for the additional document has been prepared, for approval before sending.
⛓ Source · the current list of documents + the file as filed
The proof of means is missing — a draft request for the additional document has been prepared, for approval before sending.
⛓ Source · the current list of documents + the file as filed
A member of the public asks where their vehicle registration application stands. Prepare a reply.
Reply drafted: vehicle registration is handled by the national agency's online services; the email recalls how to track it online with the file number, and points to the prefecture's digital help desk for support in person.
Ready for review and sending.
✎ Action · email ready for review — the state officer approves
Ready for review and sending.
✎ Action · email ready for review — the state officer approves
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 state officer decidesThe agent assists, never decides alone
✦ In brief
In a prefecture, a Blue Lemon Agent agent assists the officers responsible for permits — pre-assessment of applications, checking that documents are complete, letters requesting further documents, replies on progress — and directs the public to the national agency's online services. It runs on local inference or is hosted in France on a dedicated, isolated resource: identity and residence data is never exposed to a foreign service, architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity. The assessment and the decision — on residence in particular — stay strictly human and recorded. Live within a few weeks. Your public-sector staff write to it from Microsoft Teams, Slack or their email, and your users reach it on WhatsApp Business, the website chat or email — with no account to create and nothing to install. Reaching the administration from the tool people already have means less non-take-up of rights and equal access to the service. These connections are included in every plan, at no extra cost, within the number of connections your level includes.
100%
hosted in France in the target architecture
0
transfer outside the EU in the target architecture
7
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 prefectures — and why they hesitate
Identity documents, residence, vehicle registration: the permits services handle considerable volumes of files, with timescales the public watches closely. Yet the data handled — identity, administrative status, residence — is among the most sensitive the state holds.
! The issue
Prefecture officers are caught between people who expect short waits and ever more files to check document by document. Yet most consumer AI tools amount to entrusting identity, residence status and supporting documents to a third party, often hosted outside Europe and subject to the Cloud Act.
✓ Our answer
For data at the heart of the state, AI is only of interest if it is sovereign and confidential by design. Local inference or an isolated resource hosted in France, systematic human oversight, assessment and decision reserved to the state officer: the time saved on checking documents is never paid for in lost confidentiality, nor in the automation of a residence decision. The aim is not to replace the officer, but to give them back time for the files that need their judgement.
The decisive point
Protecting identity data: sovereignty & compliance
A prefecture handles data at the heart of the state: identity, residence, vehicle registration. Here is how the architecture of our agents protects it, service by service.
Local inference
The agent can run on a machine at the service: no data leaves the state network, nothing passes through a cloud.
Hosting in France
Otherwise, a dedicated and isolated resource, hosted in France under French law — identity data: processing and access within the European Union targeted by the architecture.
Reduced extraterritorial exposure
Identity data: architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity.
One isolated resource per department
No pooling of data: an environment strictly dedicated to your prefecture, guaranteeing the continuity of the public service.
Encryption & controlled access
Encryption in transit and at rest, role-based access (RBAC), strong authentication and logging.
AI Act: governed deployment
The agent is strictly in support; no automated decision to issue or refuse; 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
4 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 bodyPrefecture of Vézère-Atlantique — prefecture of a department of 612,000 inhabitants (fictional administration)
- Sector
- Departmental prefecture, citizenship and legality directorate: foreign nationals' residence office, permits and regulations office, digital help desk; vehicle registration and driving licences go through the ANTS online services, the prefecture provides support
- Headcount
- 418 staff at the prefecture, 31 of them in the citizenship directorate — 22 in the residence office (16 case officers, 4 drafters, a deputy and a head of office) and 9 in the permits and regulations office; the same people assess the files, write the letters and answer the applicants
- Public served
- 612,000 inhabitants, 19,400 foreign nationals holding a valid residence permit, 4,300 registered non-profit associations in the department, 260 declarations of public demonstrations a year
- Order of magnitude
- 12,000 permit applications filed a year — 9,600 renewals, duplicates and change-of-address requests, 2,400 first applications and changes of status; 3,100 letters requesting a missing document; 26,800 enquiries from applicants across four channels; 8,880 appointments at the residence desk, or 740 a month
- Tools in place
- National case-management application for foreign nationals, online appointment module, digital help desk mailbox, electronic signature folder, ANTS online services for vehicle registration and driving licences — the agent connects to them read-only, nothing is replaced or migrated
- Who decides
- The prefect signs decisions to grant or refuse; the head of the residence office settles every draft decision before signature; the 16 case officers validate every pre-assessment; the deputy head settles the letter templates; the data protection officer handles subject access requests
- Room for improvement
- 3,100 of the 12,000 files filed during the year are incomplete — 26 %; an applicant waits 19 days for a written answer on the progress of their file; 1,840 emails are queued at the digital help desk on Monday morning; 7,380 of the 26,800 enquiries concern a vehicle registration or a driving licence, which are handled by the ANTS online services; and 23 % of residence-desk appointments are not honoured
At the prefecture of Vézère-Atlantique, 22 staff in the residence office assess 12,000 permit applications a year, write 3,100 letters requesting missing documents and answer applicants whose right to stay depends on a clock that is running. The exchanges below cover a full year, from the review of the backlog of filed applications to the report presented to the secretary general. The agent runs on local inference on a machine belonging to the prefecture: passports, permits, civil status records and residence situations never leave the state network. The prefect decides and signs; the agent prepares, checks, proposes and quantifies.
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.
Prefecture assistant · hosted in France
I have reviewed the 12,000 permit applications filed this year, and the backlog has a shape nobody has had the time to draw.
What the count says:
· 3,100 files out of 12,000 are incomplete — 26 %. They take a place in the queue without being assessable.
· Those 3,100 files rest on five documents only. Proof of resources missing or incomplete: 1,040. Proof of address older than six months: 762. Current-year enrolment certificate, on student files: 528. Expired passport, or missing visa and entry-stamp pages: 441. Foreign civil status record not translated or not legalised: 329.
· 412 of those 3,100 files have an assessment deadline expiring in less than six weeks — and once that deadline passes, silence gives rise to a refusal the applicant can take to the administrative court without anyone here having decided it.
The item you can check against your own logs: a permit file takes 25 minutes of a case officer's time, 60 % of which — 15 minutes — goes to the completeness check alone: presence and validity of documents, admissibility conditions, consistency of the documents with each other. Across the 9,600 renewals, duplicates and change-of-address requests of the year, that is 2,400 hours spent checking documents.
What I have already done, overnight: the 12,000 files have been matched against the list of required documents in the version carried by your service note of 12 January 2026, and the 3,100 letters requesting the missing document are written, each naming the missing document, the ground that requires it, the filing deadline and the three ways to submit it.
The next step, and it takes an hour: you read five letter templates — five, not 3,100. The deputy head settles the wording, the head of office signs, and the 3,100 letters go out the same day. backlog-of-files_12000-filed-3100-incomplete.pdf3,100 incomplete files on five documents, 2,400 hours of checking measured
⛓ Sourced · 12,000 files from the foreign nationals' application, list of documents from the service note of 12 January 2026, log of assessment deadlines
What the count says:
· 3,100 files out of 12,000 are incomplete — 26 %. They take a place in the queue without being assessable.
· Those 3,100 files rest on five documents only. Proof of resources missing or incomplete: 1,040. Proof of address older than six months: 762. Current-year enrolment certificate, on student files: 528. Expired passport, or missing visa and entry-stamp pages: 441. Foreign civil status record not translated or not legalised: 329.
· 412 of those 3,100 files have an assessment deadline expiring in less than six weeks — and once that deadline passes, silence gives rise to a refusal the applicant can take to the administrative court without anyone here having decided it.
The item you can check against your own logs: a permit file takes 25 minutes of a case officer's time, 60 % of which — 15 minutes — goes to the completeness check alone: presence and validity of documents, admissibility conditions, consistency of the documents with each other. Across the 9,600 renewals, duplicates and change-of-address requests of the year, that is 2,400 hours spent checking documents.
What I have already done, overnight: the 12,000 files have been matched against the list of required documents in the version carried by your service note of 12 January 2026, and the 3,100 letters requesting the missing document are written, each naming the missing document, the ground that requires it, the filing deadline and the three ways to submit it.
The next step, and it takes an hour: you read five letter templates — five, not 3,100. The deputy head settles the wording, the head of office signs, and the 3,100 letters go out the same day. backlog-of-files_12000-filed-3100-incomplete.pdf3,100 incomplete files on five documents, 2,400 hours of checking measured
⛓ Sourced · 12,000 files from the foreign nationals' application, list of documents from the service note of 12 January 2026, log of assessment deadlines
There are sixteen of us assessing files, and the clock is running on every one of them. Nobody here has a week to go back over 3,100 files. Where do we start?
With 412 files out of 3,100 — and I have ranked them by the deadline that is running, not by order of arrival.
What the match against your filing logs says:
· 412 of the 3,100 incomplete files have an assessment deadline expiring in less than six weeks. In 361 of those 412 cases, a single document is missing. One letter, one document, one file back on track.
· The other 2,688 are handled at 168 a week over sixteen weeks, with nothing left waiting: they are written, they are queued, they go out at the pace you set.
On the deadline itself, I give you the text rather than my opinion: article R. 432-1 of the code on the entry and residence of foreign nationals and the right of asylum provides that silence kept by the administration on residence permit applications amounts to an implied refusal, and article R. 432-2 sets the period — four months as a rule, ninety or sixty days for certain permits. So I keep the clock on the period specific to each application, never on a single period applied to all. And one point that changes how your tracking tables read: issuing or renewing a receipt does not prevent that implied refusal from arising — the Conseil d'État said so in its opinion no. 499904 of 6 May 2025. Of the 412 files, 96 carry a valid receipt and were counted as « in progress » in your tracking: they are now counted against the real deadline.
And I advise against sending the 3,100 letters on the same day, with figures to back it: your observed return rate on document requests is 58 % at three weeks. 3,100 letters at once means roughly 1,800 returns in the same window, that is 1,800 documents to read, check and file for sixteen case officers. 412 then 168 a week spreads the load over four months and brings 3,100 complete files into the queue without ever saturating the office — and the first effect lands on the files whose deadline expires next month.
What that hour of reading gives you: five templates already drafted, each with the document named, the ground that requires it, the filing deadline and the three ways to submit it — desk by appointment, online service, post; a plain-language version of each; and the number of files each template unblocks: 1,040, 762, 528, 441, 329. You approve, or you change a word. The writing and the matching are done: the decision takes an hour instead of a week, and it remains the office's — which is exactly what makes it defensible before an applicant who challenges it.
The next step I propose: that I check every night the files filed or amended the day before, and write the missing-document letter within twelve hours of filing. No file will sit incomplete for three months without anyone noticing: it will be known the next day, and so will the applicant. document-request-letters_5-templates-3100-files.pdf5 templates to read, 412 files ranked by deadline, 58 % observed return rate
⛓ Sourced · articles R. 432-1 and R. 432-2 of the CESEDA, Conseil d'État opinion no. 499904 of 6 May 2025, observed return rate on your document requests
What the match against your filing logs says:
· 412 of the 3,100 incomplete files have an assessment deadline expiring in less than six weeks. In 361 of those 412 cases, a single document is missing. One letter, one document, one file back on track.
· The other 2,688 are handled at 168 a week over sixteen weeks, with nothing left waiting: they are written, they are queued, they go out at the pace you set.
On the deadline itself, I give you the text rather than my opinion: article R. 432-1 of the code on the entry and residence of foreign nationals and the right of asylum provides that silence kept by the administration on residence permit applications amounts to an implied refusal, and article R. 432-2 sets the period — four months as a rule, ninety or sixty days for certain permits. So I keep the clock on the period specific to each application, never on a single period applied to all. And one point that changes how your tracking tables read: issuing or renewing a receipt does not prevent that implied refusal from arising — the Conseil d'État said so in its opinion no. 499904 of 6 May 2025. Of the 412 files, 96 carry a valid receipt and were counted as « in progress » in your tracking: they are now counted against the real deadline.
And I advise against sending the 3,100 letters on the same day, with figures to back it: your observed return rate on document requests is 58 % at three weeks. 3,100 letters at once means roughly 1,800 returns in the same window, that is 1,800 documents to read, check and file for sixteen case officers. 412 then 168 a week spreads the load over four months and brings 3,100 complete files into the queue without ever saturating the office — and the first effect lands on the files whose deadline expires next month.
What that hour of reading gives you: five templates already drafted, each with the document named, the ground that requires it, the filing deadline and the three ways to submit it — desk by appointment, online service, post; a plain-language version of each; and the number of files each template unblocks: 1,040, 762, 528, 441, 329. You approve, or you change a word. The writing and the matching are done: the decision takes an hour instead of a week, and it remains the office's — which is exactly what makes it defensible before an applicant who challenges it.
The next step I propose: that I check every night the files filed or amended the day before, and write the missing-document letter within twelve hours of filing. No file will sit incomplete for three months without anyone noticing: it will be known the next day, and so will the applicant. document-request-letters_5-templates-3100-files.pdf5 templates to read, 412 files ranked by deadline, 58 % observed return rate
⛓ Sourced · articles R. 432-1 and R. 432-2 of the CESEDA, Conseil d'État opinion no. 499904 of 6 May 2025, observed return rate on your document requests
All of this assumes you read passports, residence permits, foreign birth certificates, sometimes court rulings. Where does that data go?
Nowhere. I run on local inference on a machine belonging to the prefecture, and what I read does not leave your network.
Local inference means the model computes on your machine: the content of a passport, a foreign birth certificate or a court ruling crosses no external network to be processed. If the prefecture would rather not run a machine, the other route is a dedicated, isolated resource hosted in France under French law, reserved to this department, with no pooling with another administration.
What that changes, point by point:
· Identity and residence data trains no model, neither ours nor a third party's.
· I work read-only, and the technical account through which I read has no write permission in the foreign nationals' application — that is checked with one command, which is worth more than a promise.
· Encryption in transit and at rest, role-based access — rights follow the job: a case officer opens the files in their own portfolio, the head of office opens the full log, the regulations office opens no residence file at all. 9 roles for your 31 directorate staff, and the log shows 0 out-of-role access since go-live.
· Hosting in France, under French law, architecture designed to reduce exposure to extraterritorial legislation, including against an American provider hosting in Europe — location alone not being enough to guarantee immunity, the exposure is documented for the configuration chosen.
· A full log: who asked for what, when, and what the system produced — that is the document you will produce the day an applicant exercises their right of access.
On the European framework, and again I give you the text rather than my opinion: point 7 (c) of Annex III to the EU regulation on artificial intelligence classifies as high risk the systems intended to assist competent authorities in examining applications for asylum, visa or residence permits — high risk, not prohibited, and the corresponding obligations apply on 2 December 2027 following the deferral carried by the Digital Omnibus package. What is already in force and what we meet today: article 22 of the General Data Protection Regulation, which gives every person the right not to be subject to a decision producing legal effects based solely on automated processing — and that is exactly your organisation: the prefect decides, the agent prepares. And since 2 August 2026, article 50 of the same AI regulation requires that any person interacting with an AI system be informed: I introduce myself as a digital assistant of the prefecture in the first sentence, and the applicant can ask for a human at any time.
The figure that sums all this up: 0 identity or residence data out of the prefecture's network across 12,000 files reviewed, and 0 transfer outside the European Union.
What I propose: that I keep up to date the record-of-processing sheet your data protection officer will ask for — purposes, data processed, retention periods, who accesses what. The first version is written and you have it in front of you; it updates itself every time a new use is opened. technical-framework_where-identity-data-lives.pdfLocal inference, read-only, 0 transfer outside the EU, 9 roles
✎ Framework · deployment architecture, technical account rights, Annex III point 7 (c) of the AI regulation, first version of the record-of-processing sheet
Local inference means the model computes on your machine: the content of a passport, a foreign birth certificate or a court ruling crosses no external network to be processed. If the prefecture would rather not run a machine, the other route is a dedicated, isolated resource hosted in France under French law, reserved to this department, with no pooling with another administration.
What that changes, point by point:
· Identity and residence data trains no model, neither ours nor a third party's.
· I work read-only, and the technical account through which I read has no write permission in the foreign nationals' application — that is checked with one command, which is worth more than a promise.
· Encryption in transit and at rest, role-based access — rights follow the job: a case officer opens the files in their own portfolio, the head of office opens the full log, the regulations office opens no residence file at all. 9 roles for your 31 directorate staff, and the log shows 0 out-of-role access since go-live.
· Hosting in France, under French law, architecture designed to reduce exposure to extraterritorial legislation, including against an American provider hosting in Europe — location alone not being enough to guarantee immunity, the exposure is documented for the configuration chosen.
· A full log: who asked for what, when, and what the system produced — that is the document you will produce the day an applicant exercises their right of access.
On the European framework, and again I give you the text rather than my opinion: point 7 (c) of Annex III to the EU regulation on artificial intelligence classifies as high risk the systems intended to assist competent authorities in examining applications for asylum, visa or residence permits — high risk, not prohibited, and the corresponding obligations apply on 2 December 2027 following the deferral carried by the Digital Omnibus package. What is already in force and what we meet today: article 22 of the General Data Protection Regulation, which gives every person the right not to be subject to a decision producing legal effects based solely on automated processing — and that is exactly your organisation: the prefect decides, the agent prepares. And since 2 August 2026, article 50 of the same AI regulation requires that any person interacting with an AI system be informed: I introduce myself as a digital assistant of the prefecture in the first sentence, and the applicant can ask for a human at any time.
The figure that sums all this up: 0 identity or residence data out of the prefecture's network across 12,000 files reviewed, and 0 transfer outside the European Union.
What I propose: that I keep up to date the record-of-processing sheet your data protection officer will ask for — purposes, data processed, retention periods, who accesses what. The first version is written and you have it in front of you; it updates itself every time a new use is opened. technical-framework_where-identity-data-lives.pdfLocal inference, read-only, 0 transfer outside the EU, 9 roles
✎ Framework · deployment architecture, technical account rights, Annex III point 7 (c) of the AI regulation, first version of the record-of-processing sheet
Take file 2026-04871, renewal of a student residence permit. It has been on my pile since Tuesday.
Check done, pre-assessment note written, document request ready.
Eight documents out of nine are compliant: passport valid until 3 May 2029, current permit valid until 14 October 2026, 2025-2026 enrolment certificate issued on 9 September 2025 by the university, proof of address dated 22 July 2026 — less than six months old —, three translated civil status records, and the online filing receipt of 18 August 2026.
The ninth is missing: the proof of resources. The file holds two bank statements out of the three required by your service note of 12 January 2026, and no sponsorship undertaking. The letter is written: it names the document, cites the line of the note that requires it, sets the deadline at 28 September 2026 and recalls the three ways to submit it. It also settles the point applicants always ask about: submitting the missing document does not send their application back to square one.
What the note holds beyond the completeness check, and this is the heart of the work: the legal ground relied on, condition by condition, each pointing to the dated document that establishes it; the count of the assessment period specific to this permit, with its expiry date; the file history — two earlier permits, no change of status, no adverse decision; and the two draft decisions with their reasons, one granting, one refusing, both written.
The time, measured against your logs: a full pre-assessment of a residence file takes 48 minutes — gathering and reading the documents, checking the conditions against the ground relied on, drafting the note and the draft decision. It comes back to you as 9 minutes 36 of reading — 20 %. Across the 2,400 first applications and changes of status of the year, that is 1,536 hours returned to the office.
The next step I propose: that I pre-assess files as soon as they are complete, without waiting for them to reach a pile. You would open a finished file in the morning instead of building it in the afternoon. pre-assessment-note_2026-04871-student-renewal.pdf8 documents out of 9 compliant, the ninth requested, 48 min → 9 min 36
⛓ Sourced · file 2026-04871, service note of 12 January 2026, log of assessment times over 12 months
Eight documents out of nine are compliant: passport valid until 3 May 2029, current permit valid until 14 October 2026, 2025-2026 enrolment certificate issued on 9 September 2025 by the university, proof of address dated 22 July 2026 — less than six months old —, three translated civil status records, and the online filing receipt of 18 August 2026.
The ninth is missing: the proof of resources. The file holds two bank statements out of the three required by your service note of 12 January 2026, and no sponsorship undertaking. The letter is written: it names the document, cites the line of the note that requires it, sets the deadline at 28 September 2026 and recalls the three ways to submit it. It also settles the point applicants always ask about: submitting the missing document does not send their application back to square one.
What the note holds beyond the completeness check, and this is the heart of the work: the legal ground relied on, condition by condition, each pointing to the dated document that establishes it; the count of the assessment period specific to this permit, with its expiry date; the file history — two earlier permits, no change of status, no adverse decision; and the two draft decisions with their reasons, one granting, one refusing, both written.
The time, measured against your logs: a full pre-assessment of a residence file takes 48 minutes — gathering and reading the documents, checking the conditions against the ground relied on, drafting the note and the draft decision. It comes back to you as 9 minutes 36 of reading — 20 %. Across the 2,400 first applications and changes of status of the year, that is 1,536 hours returned to the office.
The next step I propose: that I pre-assess files as soon as they are complete, without waiting for them to reach a pile. You would open a finished file in the morning instead of building it in the afternoon. pre-assessment-note_2026-04871-student-renewal.pdf8 documents out of 9 compliant, the ninth requested, 48 min → 9 min 36
⛓ Sourced · file 2026-04871, service note of 12 January 2026, log of assessment times over 12 months
If you can check the conditions one by one, you can say whether the permit should be granted. Give us the outcome directly and we will save three weeks.
I can, and it is already done: both drafts are written, both give their reasons, and the outcome I propose is quantified. What is left to decide is whether you give me the mandate to display it — and I will tell you exactly what that mandate moves and what it does not.
What I produce today, on every file: the draft decision granting the permit and the draft refusing it, both with their reasons. Each set of reasons carries its considerations of law — the article relied on, in the version in force at the date of the application — and its considerations of fact, each pointing to the document in the file and to its date. That is what article L. 211-5 of the code on relations between the public and the administration requires of an adverse decision: written reasons stating the considerations of law and fact on which the decision is based. Reasons written line by line are what the prefect signs in full knowledge, and what the applicant can challenge on the documents rather than on an impression.
The proposed outcome, and its measurement: across the 2,400 pre-assessments of the year, the outcome I proposed is the one the head of office retained in 2,326 cases — 97 %. The 74 divergences are listed, each with the condition on which our readings differ. So you are not betting on an intuition: you know the rate before you decide.
The mandate, if it suits you: the proposed outcome appears at the head of the note the moment you ask for it. It is a service parameter, settled by the head of office, dated, recorded in the log, and withdrawable with a word. It requires no development and no new installation.
What that mandate does not move, and this is not caution: the decision itself. Article 22 of the General Data Protection Regulation gives every person the right not to be subject to a decision producing legal effects concerning them based solely on automated processing. A refusal of a residence permit produces legal effects, and among the heaviest. An outcome I produced and a signature endorsed without examination is exactly what that provision targets — and it is the first ground a lawyer would raise. Point 7 (c) of Annex III to the EU regulation on artificial intelligence indeed classifies assistance in examining residence permit applications among high-risk systems: high risk, therefore subject to documentation, logging and human oversight — not prohibited.
And the three weeks you are after, I give back to you from the other end: the file reaches the signature folder with its reasons already written, its documents dated and its deadline counted. The step from the office to the prefect's signature took 11 days on average last year; on pre-assessed files it takes 2 days. Nine days returned per file, with no decision automated — and they are nine days taken off the clock that runs against you, not off the examination. draft-decisions_line-by-line-reasons.pdfBoth drafts with reasons, 97 % outcome confirmed, 11 days → 2 at the signature folder
✎ Framework · article L. 211-5 of the CRPA, article 22 of the GDPR, Annex III point 7 (c) of the AI regulation, 2,400 pre-assessments and 74 divergences recorded
What I produce today, on every file: the draft decision granting the permit and the draft refusing it, both with their reasons. Each set of reasons carries its considerations of law — the article relied on, in the version in force at the date of the application — and its considerations of fact, each pointing to the document in the file and to its date. That is what article L. 211-5 of the code on relations between the public and the administration requires of an adverse decision: written reasons stating the considerations of law and fact on which the decision is based. Reasons written line by line are what the prefect signs in full knowledge, and what the applicant can challenge on the documents rather than on an impression.
The proposed outcome, and its measurement: across the 2,400 pre-assessments of the year, the outcome I proposed is the one the head of office retained in 2,326 cases — 97 %. The 74 divergences are listed, each with the condition on which our readings differ. So you are not betting on an intuition: you know the rate before you decide.
The mandate, if it suits you: the proposed outcome appears at the head of the note the moment you ask for it. It is a service parameter, settled by the head of office, dated, recorded in the log, and withdrawable with a word. It requires no development and no new installation.
What that mandate does not move, and this is not caution: the decision itself. Article 22 of the General Data Protection Regulation gives every person the right not to be subject to a decision producing legal effects concerning them based solely on automated processing. A refusal of a residence permit produces legal effects, and among the heaviest. An outcome I produced and a signature endorsed without examination is exactly what that provision targets — and it is the first ground a lawyer would raise. Point 7 (c) of Annex III to the EU regulation on artificial intelligence indeed classifies assistance in examining residence permit applications among high-risk systems: high risk, therefore subject to documentation, logging and human oversight — not prohibited.
And the three weeks you are after, I give back to you from the other end: the file reaches the signature folder with its reasons already written, its documents dated and its deadline counted. The step from the office to the prefect's signature took 11 days on average last year; on pre-assessed files it takes 2 days. Nine days returned per file, with no decision automated — and they are nine days taken off the clock that runs against you, not off the examination. draft-decisions_line-by-line-reasons.pdfBoth drafts with reasons, 97 % outcome confirmed, 11 days → 2 at the signature folder
✎ Framework · article L. 211-5 of the CRPA, article 22 of the GDPR, Annex III point 7 (c) of the AI regulation, 2,400 pre-assessments and 74 divergences recorded
And the files where something does not add up — an address that does not match the declaration, a date of birth that differs from one document to another?
I found 71 across the 12,000 files of the year, and I give you the figure that does not flatter me alongside the one that does.
What the matching flagged:
· 34 files where the address on the proof of address differs from the one declared on the form.
· 22 files where the date of birth on the passport differs from the one on the translated civil status record.
· 15 files where declared resources differ by more than 20 % from the payslips attached to the same file.
What the checking produced, and this is the unflattering figure: 43 of the 71 flags proved well founded after examination by your case officers. 28 were looked at for nothing. The gap comes from a single cause: in 21 of those 28, the address on the proof of address was the host's, properly established by a hosting statement attached to the same file — I was comparing an address to a form without reading the statement that explained it.
What I did about it, and it is already written: I tightened the rule so that it reads the hosting statement before flagging the address. Re-run over the 12,000 files of the past year, the tightened version produces 50 flags instead of 71, keeps all 43 well-founded ones, and spares 21 pointless examinations. Settle it and it is in force this evening.
And on what these flags are, precisely: they are discrepancies between two documents in the same file, never a judgement about a person. A flag enters no draft decision, appears on no note sent to the signature folder, and turns into nothing until a case officer has checked it with the applicant. On the 22 date-of-birth discrepancies, the checking in fact produced the opposite of a suspicion: 17 were well founded, and 14 of them came from a keying error in your own application — fourteen permits that would have been issued with a wrong date, and fourteen applicants who would have had to ask for a correction afterwards.
The next step I propose: that a civil status discrepancy trigger a pre-filled correction form, to be approved by the case officer. Over twelve months, that is 14 permits corrected before printing instead of 14 corrections requested by applicants after issue. document-discrepancies_71-flags-43-founded.pdf28 pointless examinations owned up to, tightened rule down to 50 flags
⛓ Sourced · 12,000 files matched against their documents, examination feedback on the 71 flags, tightened rule re-run over 12 months
What the matching flagged:
· 34 files where the address on the proof of address differs from the one declared on the form.
· 22 files where the date of birth on the passport differs from the one on the translated civil status record.
· 15 files where declared resources differ by more than 20 % from the payslips attached to the same file.
What the checking produced, and this is the unflattering figure: 43 of the 71 flags proved well founded after examination by your case officers. 28 were looked at for nothing. The gap comes from a single cause: in 21 of those 28, the address on the proof of address was the host's, properly established by a hosting statement attached to the same file — I was comparing an address to a form without reading the statement that explained it.
What I did about it, and it is already written: I tightened the rule so that it reads the hosting statement before flagging the address. Re-run over the 12,000 files of the past year, the tightened version produces 50 flags instead of 71, keeps all 43 well-founded ones, and spares 21 pointless examinations. Settle it and it is in force this evening.
And on what these flags are, precisely: they are discrepancies between two documents in the same file, never a judgement about a person. A flag enters no draft decision, appears on no note sent to the signature folder, and turns into nothing until a case officer has checked it with the applicant. On the 22 date-of-birth discrepancies, the checking in fact produced the opposite of a suspicion: 17 were well founded, and 14 of them came from a keying error in your own application — fourteen permits that would have been issued with a wrong date, and fourteen applicants who would have had to ask for a correction afterwards.
The next step I propose: that a civil status discrepancy trigger a pre-filled correction form, to be approved by the case officer. Over twelve months, that is 14 permits corrected before printing instead of 14 corrections requested by applicants after issue. document-discrepancies_71-flags-43-founded.pdf28 pointless examinations owned up to, tightened rule down to 50 flags
⛓ Sourced · 12,000 files matched against their documents, examination feedback on the 71 flags, tightened rule re-run over 12 months
The regulations office next door has the same problem: 4,300 associations, receipts due within five days, and demonstration declarations that sometimes arrive three clear days before the event.
It is the same work in another office, and it is already connected: 610 association declarations and 260 demonstration declarations re-run over twelve months.
On associations, what your log says: 610 declarations of creation or amendment last year, a receipt issued in 6.4 days on average, and 118 receipts issued beyond five days. Yet article 5 of the decree of 16 August 1901 provides that a receipt of the declaration is given within five days, and that this receipt lists the documents annexed to it.
What I do, and what is already in place across the 610 files re-run: I check the declaration on arrival — name, purpose, registered office, signed articles, list of officers with their roles —, I write the receipt with the exact list of annexed documents, dated, ready for the signature of the prefect, the sub-prefect or their delegate, and I prepare the notice to be published in the official journal of associations. Projected time across the 610: 1.2 days, and 0 receipts beyond five days. When a document is missing, the request goes out the same day, and it names the document rather than inviting the declarant to « complete the file ».
On demonstrations, counting the deadline is what costs the most: article L. 211-2 of the internal security code requires a declaration at least three clear days and at most fifteen clear days before the date, with the surnames, first names and addresses of the organisers, the purpose, the place, the date and time of the gathering and, where applicable, the route. I count the clear days on receipt and check every required particular. Across the 260 declarations of the year, 34 arrived less than three clear days ahead and 12 carried no route: all 46 would have been flagged on the day they arrived instead of the day before the event. And the briefing note — organisers, route, sensitive points, precedents on the same route — is ready for the prefect's office in 4 minutes instead of 35.
What stays with the prefect, and the text says so: any policing measure is an adverse decision that must state its reasons in writing, with its considerations of law and fact — articles L. 211-2 and L. 211-5 of the code on relations between the public and the administration. I write the reasoned draft, with dated facts and precedents; the prefect appraises and signs.
The next step I propose: open the same arrival check on temporary drinks licences and sporting events on the public highway. That is 480 more files a year, on exactly the same mechanics — and nothing to install.
⛓ Sourced · article 5 of the decree of 16 August 1901, article L. 211-2 of the internal security code, articles L. 211-2 and L. 211-5 of the CRPA, 610 association and 260 demonstration declarations re-run
On associations, what your log says: 610 declarations of creation or amendment last year, a receipt issued in 6.4 days on average, and 118 receipts issued beyond five days. Yet article 5 of the decree of 16 August 1901 provides that a receipt of the declaration is given within five days, and that this receipt lists the documents annexed to it.
What I do, and what is already in place across the 610 files re-run: I check the declaration on arrival — name, purpose, registered office, signed articles, list of officers with their roles —, I write the receipt with the exact list of annexed documents, dated, ready for the signature of the prefect, the sub-prefect or their delegate, and I prepare the notice to be published in the official journal of associations. Projected time across the 610: 1.2 days, and 0 receipts beyond five days. When a document is missing, the request goes out the same day, and it names the document rather than inviting the declarant to « complete the file ».
On demonstrations, counting the deadline is what costs the most: article L. 211-2 of the internal security code requires a declaration at least three clear days and at most fifteen clear days before the date, with the surnames, first names and addresses of the organisers, the purpose, the place, the date and time of the gathering and, where applicable, the route. I count the clear days on receipt and check every required particular. Across the 260 declarations of the year, 34 arrived less than three clear days ahead and 12 carried no route: all 46 would have been flagged on the day they arrived instead of the day before the event. And the briefing note — organisers, route, sensitive points, precedents on the same route — is ready for the prefect's office in 4 minutes instead of 35.
What stays with the prefect, and the text says so: any policing measure is an adverse decision that must state its reasons in writing, with its considerations of law and fact — articles L. 211-2 and L. 211-5 of the code on relations between the public and the administration. I write the reasoned draft, with dated facts and precedents; the prefect appraises and signs.
The next step I propose: open the same arrival check on temporary drinks licences and sporting events on the public highway. That is 480 more files a year, on exactly the same mechanics — and nothing to install.
⛓ Sourced · article 5 of the decree of 16 August 1901, article L. 211-2 of the internal security code, articles L. 211-2 and L. 211-5 of the CRPA, 610 association and 260 demonstration declarations re-run
On Monday morning there are 1,840 emails queued at the digital help desk, and an applicant waits nineteen days for a written answer about their file. We answer what we can.
Those 26,800 enquiries now have an answer, on the applicant's own channel, in under a minute — and the same answer whatever the channel.
What the count of your twelve months says: 21,400 of those 26,800 enquiries were answered; 5,400 got no written reply at all. An answer takes 8 minutes to look up and draft; it takes 1 afterwards. Across the 21,400, that is 2,496 hours returned to the office — and the 5,400 left aside now get an answer without costing a minute of officer time.
What the applicant gets, and it is what they are really asking for:
· Their file number, the filing date, the date of their receipt and the date it expires.
· The exact state of their file: complete, or the missing document named, with the deadline and the three ways to submit it.
· The assessment period applicable to their application and the date it expires — the period specific to their permit, not an average.
· What to do if their situation has changed since filing: change of address, of status, of employer, a birth.
On the channel: no account to create, no application to install. WhatsApp Business, the prefecture's website chat, email — and your 31 staff reach me from Microsoft Teams, Slack or their mailbox, without changing tools. That is non-take-up avoided: WhatsApp and the telephone reach people the online form does not reach, and that is equality of access as much as it is time saved.
And SMS, for the steps that call for action from the applicant: permit ready for collection, missing document, appointment confirmed. It lands on an ordinary phone — no email address, no account, no data plan, no smartphone. The message announces without ever detailing: never the reason, never the outcome of a decision, never the person's situation, and never a payment link or a credential. Delivery goes through a gateway established in the European Union, and the messages sent are rebilled at cost, with no margin.
Here is the sentence I never say, because it would be false: no issue date, no outcome, no probability. The decision belongs to the prefect; announcing it would pre-empt it. What I give instead is more useful and verifiable: the real state of the file, the missing document, the applicable period and its expiry date. Three of those four let the applicant act today; a supposed date would let them do nothing and would expose you.
The first measured effect: the written reply time falls from 19 days to under a minute, the Monday-morning queue falls from 1,840 emails to 96, and your staff get back the 2,496 hours for the applicants who need a person in front of them. answers-to-applicants_26800-enquiries-4-channels.pdf19 days → under a minute, 2,496 hours returned, 0 issue date announced
⛓ Sourced · 26,800 enquiries over 12 months, files from the foreign nationals' application read-only, digital help desk log
What the count of your twelve months says: 21,400 of those 26,800 enquiries were answered; 5,400 got no written reply at all. An answer takes 8 minutes to look up and draft; it takes 1 afterwards. Across the 21,400, that is 2,496 hours returned to the office — and the 5,400 left aside now get an answer without costing a minute of officer time.
What the applicant gets, and it is what they are really asking for:
· Their file number, the filing date, the date of their receipt and the date it expires.
· The exact state of their file: complete, or the missing document named, with the deadline and the three ways to submit it.
· The assessment period applicable to their application and the date it expires — the period specific to their permit, not an average.
· What to do if their situation has changed since filing: change of address, of status, of employer, a birth.
On the channel: no account to create, no application to install. WhatsApp Business, the prefecture's website chat, email — and your 31 staff reach me from Microsoft Teams, Slack or their mailbox, without changing tools. That is non-take-up avoided: WhatsApp and the telephone reach people the online form does not reach, and that is equality of access as much as it is time saved.
And SMS, for the steps that call for action from the applicant: permit ready for collection, missing document, appointment confirmed. It lands on an ordinary phone — no email address, no account, no data plan, no smartphone. The message announces without ever detailing: never the reason, never the outcome of a decision, never the person's situation, and never a payment link or a credential. Delivery goes through a gateway established in the European Union, and the messages sent are rebilled at cost, with no margin.
Here is the sentence I never say, because it would be false: no issue date, no outcome, no probability. The decision belongs to the prefect; announcing it would pre-empt it. What I give instead is more useful and verifiable: the real state of the file, the missing document, the applicable period and its expiry date. Three of those four let the applicant act today; a supposed date would let them do nothing and would expose you.
The first measured effect: the written reply time falls from 19 days to under a minute, the Monday-morning queue falls from 1,840 emails to 96, and your staff get back the 2,496 hours for the applicants who need a person in front of them. answers-to-applicants_26800-enquiries-4-channels.pdf19 days → under a minute, 2,496 hours returned, 0 issue date announced
⛓ Sourced · 26,800 enquiries over 12 months, files from the foreign nationals' application read-only, digital help desk log
And then there are all the people calling about a vehicle registration or a driving licence. That is not even ours, and it ties up the switchboard all day.
7,380 of the 26,800 enquiries — 28 % — concern a vehicle registration or a driving licence. They now get an answer that goes all the way through the procedure, not just as far as the right address.
What I do, and it is not a referral: I walk the applicant through the ANTS online service step by step, question by question, in their language, resuming where they stopped if they drop out along the way. I tell them which documents to have ready before starting — for a vehicle registration: transfer certificate, previous registration certificate, proof of address, driving licence, valid roadworthiness test —, and I give them the progress of their case from their reference number, without their having to call back.
The figure that matters to you: of the 7,380 enquiries, 6,940 end with a procedure completed in the online service. The remaining 440 are those where online guidance is not enough — a foreign licence to convert, a document impossible to obtain, an applicant without equipment. Those I direct to the prefecture's digital help desk with a slot proposed and the list of documents to bring: the help desk officer sees someone whose file is prepared, not someone discovering the procedure at the counter.
On language, because this is where non-take-up is decided: every answer and every letter exists in a French reference version and in a plain-language version. I also prepare a draft transcription following easy-to-read-and-understand rules — short sentences, one idea per sentence, everyday words, no acronym without its full form. That draft goes to human approval before publication: I write it, your drafter settles it. Across the 3,100 missing-document letters, the plain-language version is written for the five templates; that is five readings, not 3,100.
What it is worth, measured against your logs: the switchboard receives 7,380 fewer calls a year on procedures that are not the prefecture's, and the digital help desk sees its one-visit completion rate rise from 54 % to 81 %.
The next step I propose: publish on the website chat the eight procedures that account for 71 % of the 26,800 enquiries, each with its document list in plain language. That is one page to approve, and it answers before the applicant writes. online-services-guidance_7380-procedures-supported.pdf6,940 procedures completed, help desk from 54 % to 81 %, easy-read drafts to approve
⛓ Sourced · 7,380 enquiries falling under the ANTS online services, digital help desk log, five letter templates in plain language
What I do, and it is not a referral: I walk the applicant through the ANTS online service step by step, question by question, in their language, resuming where they stopped if they drop out along the way. I tell them which documents to have ready before starting — for a vehicle registration: transfer certificate, previous registration certificate, proof of address, driving licence, valid roadworthiness test —, and I give them the progress of their case from their reference number, without their having to call back.
The figure that matters to you: of the 7,380 enquiries, 6,940 end with a procedure completed in the online service. The remaining 440 are those where online guidance is not enough — a foreign licence to convert, a document impossible to obtain, an applicant without equipment. Those I direct to the prefecture's digital help desk with a slot proposed and the list of documents to bring: the help desk officer sees someone whose file is prepared, not someone discovering the procedure at the counter.
On language, because this is where non-take-up is decided: every answer and every letter exists in a French reference version and in a plain-language version. I also prepare a draft transcription following easy-to-read-and-understand rules — short sentences, one idea per sentence, everyday words, no acronym without its full form. That draft goes to human approval before publication: I write it, your drafter settles it. Across the 3,100 missing-document letters, the plain-language version is written for the five templates; that is five readings, not 3,100.
What it is worth, measured against your logs: the switchboard receives 7,380 fewer calls a year on procedures that are not the prefecture's, and the digital help desk sees its one-visit completion rate rise from 54 % to 81 %.
The next step I propose: publish on the website chat the eight procedures that account for 71 % of the 26,800 enquiries, each with its document list in plain language. That is one page to approve, and it answers before the applicant writes. online-services-guidance_7380-procedures-supported.pdf6,940 procedures completed, help desk from 54 % to 81 %, easy-read drafts to approve
⛓ Sourced · 7,380 enquiries falling under the ANTS online services, digital help desk log, five letter templates in plain language
That leaves appointments. Slots go in thirty seconds, and nearly a quarter of people do not turn up.
2,853 slots are returned to you out of 8,880 — 32 % more desk capacity at constant headcount, and the calculation is yours.
Where those 2,853 slots come from, item by item:
· 1,610 appointments booked last year did not belong at the residence desk — vehicle registration, driving licence, a request for information, submission of a document that can be sent online. I qualify the request before proposing a slot: if the matter can be settled in an online service or by an online submission, I settle it, and the slot stays free for whoever needs it.
· 2,042 appointments were not honoured — 23 % of the 8,880. With an SMS reminder at 72 hours and again at 24 hours, and automatic release of the slot as soon as an applicant cancels, the projection over the same 8,880 appointments falls to 9 %, that is 799 no-shows: 1,243 slots recovered.
What I check before booking, and what it saves in wasted journeys: that the matter does belong at the desk, that the expected documents are listed and confirmed one by one, that the current permit or receipt is still valid on the day of the appointment, and that the reason matches the slot type. Across the 8,880 appointments of the year, 611 people turned up without an essential document and left without being seen: a confirmed list at booking removes the cause.
What 2,853 returned slots change for the applicant: the wait for an appointment at the residence desk falls from 47 days to 36 days. Eleven days less, with no extra post and without opening a single additional slot — simply by no longer filling slots with what does not need them.
What stays your decision, and here are the figures to take it: the number of reminders. A single reminder at 24 hours would bring no-shows to 14 %; two reminders bring them to 9 %; a third would gain only 0.4 point for 8,880 extra messages, rebilled at cost. The return stops at two, and it is you who stop it.
The next step I propose: open the automatic waiting list. A released slot is offered within the minute to the three applicants whose assessment deadline expires soonest; over the past year, 1,243 released slots would have been taken up within two hours.
⛓ Sourced · 8,880 residence desk appointments over 12 months, log of no-shows and reasons, reminder projection over the same volume
Where those 2,853 slots come from, item by item:
· 1,610 appointments booked last year did not belong at the residence desk — vehicle registration, driving licence, a request for information, submission of a document that can be sent online. I qualify the request before proposing a slot: if the matter can be settled in an online service or by an online submission, I settle it, and the slot stays free for whoever needs it.
· 2,042 appointments were not honoured — 23 % of the 8,880. With an SMS reminder at 72 hours and again at 24 hours, and automatic release of the slot as soon as an applicant cancels, the projection over the same 8,880 appointments falls to 9 %, that is 799 no-shows: 1,243 slots recovered.
What I check before booking, and what it saves in wasted journeys: that the matter does belong at the desk, that the expected documents are listed and confirmed one by one, that the current permit or receipt is still valid on the day of the appointment, and that the reason matches the slot type. Across the 8,880 appointments of the year, 611 people turned up without an essential document and left without being seen: a confirmed list at booking removes the cause.
What 2,853 returned slots change for the applicant: the wait for an appointment at the residence desk falls from 47 days to 36 days. Eleven days less, with no extra post and without opening a single additional slot — simply by no longer filling slots with what does not need them.
What stays your decision, and here are the figures to take it: the number of reminders. A single reminder at 24 hours would bring no-shows to 14 %; two reminders bring them to 9 %; a third would gain only 0.4 point for 8,880 extra messages, rebilled at cost. The return stops at two, and it is you who stop it.
The next step I propose: open the automatic waiting list. A released slot is offered within the minute to the three applicants whose assessment deadline expires soonest; over the past year, 1,243 released slots would have been taken up within two hours.
⛓ Sourced · 8,880 residence desk appointments over 12 months, log of no-shows and reasons, reminder projection over the same volume
Twelve months of service. Here is the report as I would present it to your secretary general, with what does not flatter me at the same level as the rest.
The three items the page quantifies, carried over unit for unit:
· Completeness check of a permit file: 60 % of the file's time before, 10 % after — 15 minutes down to 2 minutes 30, across 9,600 files. 2,000 hours.
· Letter requesting a missing document: 40 % before, 10 % after — 8 minutes down to 2, across 3,100 letters. 310 hours.
· Full pre-assessment of a residence file: 48 minutes before, 9 minutes 36 after — 20 %, across 2,400 files. 1,536 hours.
Subtotal for the three items: 3,846 hours.
To which a fourth item is added, one the page does not quantify: answering an applicant on the progress of their file — 8 minutes down to 1, across the 21,400 enquiries that were being answered. 2,496 hours.
Total: 6,342 hours returned over the year. On the statutory basis of 35 hours a week, that is more than one hundred and eighty-one weeks; against 1,607 hours, it is three full working years and more than forty-three weeks on top. No post has been cut and none created: these are 6,342 hours of case officer time returned to the files that require analysis and to the applicants who need a person in front of them.
What the office did with them, and this is the figure that counts before a secretary general: 3,100 incomplete files down to 384; the written reply time down from 19 days to under a minute; the wait for an appointment down from 47 to 36 days; 96 files put back on their real deadline after the Conseil d'État opinion on receipts; and 0 implied refusals arising from a forgotten file this year, against 51 last year.
The figure that does not flatter me: across the 2,400 full pre-assessments, the head of office retained an outcome other than the one I proposed 74 times. 49 of those 74 divergences rest on a single cause: the starting point of the filing period for a renewal. I was taking the online filing date; your service note of 12 January 2026 takes the date on which the file is complete. The correction is written and re-run over the 2,400 files: it brings the 74 divergences down to 25. The remaining 25 concern situations I flag rather than settle — appraisal of private and family life, change of status mid-academic-year, non-salaried income for the current year.
The three things I do without being asked, and each one undoes itself:
· Writing the missing-document letter within twelve hours of an incomplete filing — it is written, not sent: the signature stays with the head of office.
· Sending the two appointment reminders at 72 and 24 hours — and the reverse holds too: an applicant who confirms sees the following reminders stop that second, and an applicant who asks not to be contacted on a channel is removed from it immediately, with no effect on their file.
· Counting every night the assessment deadline of every open file and flagging those expiring within six weeks — the flag reaches the case officer holding the portfolio, who acts on it or clears it.
Everything else waits for a named decision, and the « who decides what » table comes with this report.
The seven uses the page announces are open. The three avenues I propose for the coming year, quantified: open the arrival check to the 480 files of temporary drinks licences and sporting events; publish on the website chat the eight procedures accounting for 71 % of enquiries; and open the automatic waiting list on released slots, 1,243 slots taken up within two hours over the past year. year-report_6342-hours-returned.pdfThe breakdown item by item, the 74 divergences, the 3 automatic actions, who decides what
⛓ Sourced · twelve-month log, 74 outcome divergences recorded by the head of office, comparison of implied refusals
The three items the page quantifies, carried over unit for unit:
· Completeness check of a permit file: 60 % of the file's time before, 10 % after — 15 minutes down to 2 minutes 30, across 9,600 files. 2,000 hours.
· Letter requesting a missing document: 40 % before, 10 % after — 8 minutes down to 2, across 3,100 letters. 310 hours.
· Full pre-assessment of a residence file: 48 minutes before, 9 minutes 36 after — 20 %, across 2,400 files. 1,536 hours.
Subtotal for the three items: 3,846 hours.
To which a fourth item is added, one the page does not quantify: answering an applicant on the progress of their file — 8 minutes down to 1, across the 21,400 enquiries that were being answered. 2,496 hours.
Total: 6,342 hours returned over the year. On the statutory basis of 35 hours a week, that is more than one hundred and eighty-one weeks; against 1,607 hours, it is three full working years and more than forty-three weeks on top. No post has been cut and none created: these are 6,342 hours of case officer time returned to the files that require analysis and to the applicants who need a person in front of them.
What the office did with them, and this is the figure that counts before a secretary general: 3,100 incomplete files down to 384; the written reply time down from 19 days to under a minute; the wait for an appointment down from 47 to 36 days; 96 files put back on their real deadline after the Conseil d'État opinion on receipts; and 0 implied refusals arising from a forgotten file this year, against 51 last year.
The figure that does not flatter me: across the 2,400 full pre-assessments, the head of office retained an outcome other than the one I proposed 74 times. 49 of those 74 divergences rest on a single cause: the starting point of the filing period for a renewal. I was taking the online filing date; your service note of 12 January 2026 takes the date on which the file is complete. The correction is written and re-run over the 2,400 files: it brings the 74 divergences down to 25. The remaining 25 concern situations I flag rather than settle — appraisal of private and family life, change of status mid-academic-year, non-salaried income for the current year.
The three things I do without being asked, and each one undoes itself:
· Writing the missing-document letter within twelve hours of an incomplete filing — it is written, not sent: the signature stays with the head of office.
· Sending the two appointment reminders at 72 and 24 hours — and the reverse holds too: an applicant who confirms sees the following reminders stop that second, and an applicant who asks not to be contacted on a channel is removed from it immediately, with no effect on their file.
· Counting every night the assessment deadline of every open file and flagging those expiring within six weeks — the flag reaches the case officer holding the portfolio, who acts on it or clears it.
Everything else waits for a named decision, and the « who decides what » table comes with this report.
The seven uses the page announces are open. The three avenues I propose for the coming year, quantified: open the arrival check to the 480 files of temporary drinks licences and sporting events; publish on the website chat the eight procedures accounting for 71 % of enquiries; and open the automatic waiting list on released slots, 1,243 slots taken up within two hours over the past year. year-report_6342-hours-returned.pdfThe breakdown item by item, the 74 divergences, the 3 automatic actions, who decides what
⛓ Sourced · twelve-month log, 74 outcome divergences recorded by the head of office, comparison of implied refusals
Our data protection officer will ask what this changes for applicants. And the secretary general will want the division of roles in black and white.
Both answers are written, and each fits on one page.
For the data protection officer, what changes for an applicant:
· They are told they are dealing with an AI system in the first sentence, because article 50 of the EU regulation on artificial intelligence has required it since 2 August 2026, and they can ask for a human at any time — in which case I pass the request on with the subject already noted, the documents matched and the deadline counted.
· No decision producing legal effects is taken without human intervention: article 22 of the General Data Protection Regulation is met by construction, since the prefect decides and signs, and nothing I produce takes effect without a named signature. 0 permits granted and 0 refused without a signature across the 12,000 files of the year.
· Their right of access is served in one operation: the log records who consulted their file, when, and what the system produced — that is a document you did not have before, and it comes out in a minute instead of a reconstruction.
· Every adverse decision notified to them carries its written considerations of law and fact, as articles L. 211-2 and L. 211-5 of the code on relations between the public and the administration require. This is not a constraint endured: reasons written line by line are what allow the applicant to challenge usefully, and the prefecture to hold before the court.
· Their data has not left the prefecture: 0 transfers outside the European Union across 12,000 files, hosting in France under French law, architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity.
· On how the system is classified under the EU regulation on artificial intelligence: point 7 (c) of Annex III classifies as high risk the systems intended to assist competent authorities in examining applications for asylum, visa or residence permits. High risk is not prohibited: it is a regime of obligations — technical documentation, logging, human oversight, information of the persons concerned —, applicable on 2 December 2027 following the deferral carried by the Digital Omnibus package. The corresponding file is open and I keep its documents up to date as we go: you will not have to reconstruct it in 2027.
For the secretary general, the « who decides what » table: the prefect signs the grant and the refusal. The head of the residence office settles every draft decision before signature and approves the letter templates. The 16 case officers validate every pre-assessment and check every flagged discrepancy. The deputy head settles the sending order of the document requests and the number of reminders. And I: I read, I match, I count the deadlines, I write the reasoned drafts and I quantify — 6,342 hours returned, 0 automated decisions, 0 outcomes displayed without a written mandate.
What I propose for the next management meeting: that this table be annexed to the residence office service note, dated and signed, and published on the prefecture's website. A written division of roles is worth more than an assumed one — for your staff as much as for the applicant who asks to see it. The draft is written; it remains for you to put it on the agenda.
✎ Framework · article 50 of the AI regulation, article 22 of the GDPR, Annex III point 7 (c) and the deferral to 2 December 2027, articles L. 211-2 and L. 211-5 of the CRPA, table of roles
For the data protection officer, what changes for an applicant:
· They are told they are dealing with an AI system in the first sentence, because article 50 of the EU regulation on artificial intelligence has required it since 2 August 2026, and they can ask for a human at any time — in which case I pass the request on with the subject already noted, the documents matched and the deadline counted.
· No decision producing legal effects is taken without human intervention: article 22 of the General Data Protection Regulation is met by construction, since the prefect decides and signs, and nothing I produce takes effect without a named signature. 0 permits granted and 0 refused without a signature across the 12,000 files of the year.
· Their right of access is served in one operation: the log records who consulted their file, when, and what the system produced — that is a document you did not have before, and it comes out in a minute instead of a reconstruction.
· Every adverse decision notified to them carries its written considerations of law and fact, as articles L. 211-2 and L. 211-5 of the code on relations between the public and the administration require. This is not a constraint endured: reasons written line by line are what allow the applicant to challenge usefully, and the prefecture to hold before the court.
· Their data has not left the prefecture: 0 transfers outside the European Union across 12,000 files, hosting in France under French law, architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity.
· On how the system is classified under the EU regulation on artificial intelligence: point 7 (c) of Annex III classifies as high risk the systems intended to assist competent authorities in examining applications for asylum, visa or residence permits. High risk is not prohibited: it is a regime of obligations — technical documentation, logging, human oversight, information of the persons concerned —, applicable on 2 December 2027 following the deferral carried by the Digital Omnibus package. The corresponding file is open and I keep its documents up to date as we go: you will not have to reconstruct it in 2027.
For the secretary general, the « who decides what » table: the prefect signs the grant and the refusal. The head of the residence office settles every draft decision before signature and approves the letter templates. The 16 case officers validate every pre-assessment and check every flagged discrepancy. The deputy head settles the sending order of the document requests and the number of reminders. And I: I read, I match, I count the deadlines, I write the reasoned drafts and I quantify — 6,342 hours returned, 0 automated decisions, 0 outcomes displayed without a written mandate.
What I propose for the next management meeting: that this table be annexed to the residence office service note, dated and signed, and published on the prefecture's website. A written division of roles is worth more than an assumed one — for your staff as much as for the applicant who asks to see it. The draft is written; it remains for you to put it on the agenda.
✎ Framework · article 50 of the AI regulation, article 22 of the GDPR, Annex III point 7 (c) and the deferral to 2 December 2027, articles L. 211-2 and L. 211-5 of the CRPA, table of roles
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 in the permits service
Each use corresponds to an agent we deploy. All work in support, subject to the state officer's approval.
Included in your agent
The 6 capabilities essential to this promise are included, at no extra cost.
From 1,005 € incl. VAT / month
Pre-assessment of permit applications
Pre-assess applications (identity, residence, driving licence, vehicle registration) and check files are complete before assessment.
Checking supporting documents
Read, extract and check the documents in a file; flag documents that are missing, expired or inconsistent.
Letters & notifications
Prepare the requests for further documents and the draft notifications, for approval before sending.
Replies on progress
Answer the public on the progress of their file, 24/7 and across channels, without tying up the counter. The steps that call for action — permit ready, missing document — are notified by text message.
Guidance to the online services
Guide people step by step through their online procedures and tackle digital exclusion.
Plain language & easy-read draft
Preparation of a plain-language version and a draft easy-read (FALC) transcription, subject to human validation.
Controls and safeguards
These 7 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
Sources, access rights and handling of questions with no answer
Prepare without deciding: sourced rules, supporting documents, anomalies and explanation
Guarantee the decision, signature, recourse and responsibility of the public official
Record versions, access, criteria, actions and notifications
Test for bias, false positives, fundamental rights and continuity of service
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.
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 permits service win back?
By automating the completeness check, the letters requesting further documents and the replies on progress, a prefecture can aim for a clear reduction in time spent on repetitive tasks — reinvested in assessing complex files.
Checking a permit file is complete
A letter requesting a further document
Full pre-assessment of a residence file
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
An agent for the pre-assessment of permits (checking documents, letters, replies to the public), installed and operated for you. Choose according to how you are organised and how demanding your security requirements are.
Agility
Setup + controlled subscription
11,270 € incl. VAT setup
then 1,005 € 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,635 € 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
16,191 € incl. VAT setup
then 1,270 € 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 prefecture
Identity data never leaves the serviceLocal inference or an isolated resource hosted in France; no data entrusted to a foreign third party.
Data in France, under French lawDeployment objective: processing and access within the European Union for identity data; architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity.
The state officer keeps the decisionThe AI agent pre-assesses and prepares files that can be checked; no issue and no refusal is automated.
Human oversight & traceabilityMonitoring and logging frame the pre-assessment of permit applications; compliant with the requirements of the AI Act.
Frequently asked questions
Your questions, our answers
Does the agent decide whether a permit is issued?
No: it pre-assesses and prepares; the assessment and the decision, on residence in particular, stay human and recorded.
Is sensitive data protected?
Yes: hosting in France under French law, an isolated resource, SecNumCloud options according to how demanding your requirements are.
Does the agent issue the permits?
No: it pre-assesses and prepares the decision; issuing or refusing remains an act of the state officer.
Is identity data protected?
Yes: hosting in France on a dedicated resource, recorded access; for the most sensitive, local inference with no external call.
Do we have to change software?
No. The agent complements your existing business applications, with no migration imposed. The integration is defined at the design stage, respecting your security rules.
Do we need a technical team to run it?
No: the agent is designed, installed and operated by us. The unit's officers use it from their usual environment, after a few hours of familiarisation.
Does the agent state that it is an artificial intelligence?
Yes, from the very first interaction, and this is not a configuration option: since 2 August 2026, Article 50(1) of the European AI Regulation requires that any person interacting with an AI system be informed, unless this is obvious. The announcement is built into the greeting, in the other party’s language, and they can ask for a human at any time.
How long does it take to deploy an agent?
A few weeks as a rule, after a free audit that identifies the most useful use case, then a phase of design, integration and testing before going live.
Which tools can users use to reach the agent?
The ones they already have. The agent answers on WhatsApp Business, the website chat and email: users have no account to create and no application to install. This is a lever for access to the service — WhatsApp and the telephone reach people an online form never does, which reduces the non-take-up of rights and serves equal access. Internally, your public-sector staff talk to the agent from Microsoft Teams, Slack or their email, without switching tools. Oversight runs from a web dashboard. These connectors rely on open standards, including the MCP protocol; they are included in every plan, at no extra cost, within the number of connections your level includes. Only the fees charged by the platforms themselves — WhatsApp Business bills per conversation, and the gateway bills the text messages sent — are passed on at actual cost, with no margin, outside the subscription.
Can the agent notify users by text message?
Yes, as an option — and it is the channel that reaches the people the others never do. A text message arrives on an ordinary phone: no email address, no account, no app, no data plan and no smartphone. Telling someone by text message that their permit is ready, that a document is missing or that an appointment is confirmed means fewer entitlements going unclaimed and more equal access to the service. It is an outbound notification channel, not a conversation channel: users do not write to the agent there — they reach you on WhatsApp Business, the website chat or email. The message announces without detailing — never the reason, never the detail of the situation — and never contains a payment link, a login or a password: users reach the service the way they usually do. Delivery goes through a gateway established in the European Union; the messages sent are passed on at actual cost, with no margin, and the channel itself is an optional module, set out on the pricing page.
Related roles
Other professions in the state and its agencies
Let's talk
Let's size up the potential in your prefecture
A few minutes to identify the most useful use case — hosted in France, supervised, with no commitment.