● Public sector — School administration
AI agent for the school administration officer
An assistant that handles enrolments, answers families and prepares the invoicing for out-of-school care — the officer keeps control of the placements. Hosted in France, on a resource isolated for each authority, children's and families' data never leaves the European Union. The AI agent assists, the officer decides.
Hosted in France
Families' data protected
GDPR & AI Act: governed deployment
Human oversight
Updated on
Deployed in a few weeks
School administration assistant · hosted in France
Check this nursery-class enrolment application for September.
Application checked. Documents present: family record book, proof of address, vaccinations up to date. The address does fall within the catchment of Jules-Ferry school. Missing: the court order setting the child's residence, mentioned in the form.
Letter requesting the document prepared.
⛓ Source · the family's file + the town's school catchment map
Letter requesting the document prepared.
⛓ Source · the family's file + the town's school catchment map
Prepare the May school-meal invoices, with the means-tested rate.
Invoicing prepared. May attendance reconciled with the bookings, rates applied according to the current means-tested bands, twelve discrepancies flagged (authorised absences to check). Notices to families generated from your templates.
Nothing is sent without your approval.
✎ Action · notices ready for review — the officer approves
Nothing is sent without your approval.
✎ Action · notices ready for review — the 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 officer decidesThe AI agent assists, it never places a child alone
✦ In brief
In the school administration department, a Blue Lemon Agent agent assists the officer with the repetitive tasks — school and out-of-school enrolment, checking documents, replies to families, lists, timetables and means-tested invoicing. It runs on local inference or is hosted in France on a resource dedicated to and isolated for each authority: children's and families' data is never exposed to a foreign service, architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity. Placements and catchment exemptions remain decided by the officer and the elected member concerned; the time won back goes to serving families. Live within a few weeks. Your public-sector staff write to it from Microsoft Teams, Slack or their email, and families 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 school departments — and why they hesitate
Enrolment peaks in the spring, families calling about school meals or the holiday club, means-tested invoicing to produce every month: the school department juggles large volumes and sensitive data — children's data.
! The issue
The school administration officer is caught between families who expect quick answers — enrolment, school meals, rates, timetables — and seasonal campaigns that overwhelm the department. Yet most consumer AI tools would amount to entrusting children's identities, means-test bands and families' circumstances to a third party, often hosted outside Europe and subject to the Cloud Act.
✓ Our answer
For children's data, 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, placements and exemptions reserved to the officer and the elected member: the time saved on enrolment and invoicing is never paid for in lost confidentiality. The aim is not to replace the officer, but to give them back time for families.
The decisive point
Protecting families' data: sovereignty & compliance
A school department handles the data of the children and families of the whole town. Here is how the architecture of our agents protects it, authority by authority.
Local inference
The agent can run on a machine belonging to the authority: no data leaves the network, nothing passes through a cloud.
Hosting in France
Otherwise, a dedicated and isolated resource, hosted in France under French law — families' data: processing and access within the European Union targeted by the architecture.
Reduced extraterritorial exposure
For children's data, the architecture aims to reduce exposure to the Cloud Act and FISA 702; being located in France or in the European Union does not, on its own, guarantee immunity.
One isolated resource per authority
No pooling of data: an environment strictly dedicated to your authority, 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 placement or exemption is automated; 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 bodyTown of Vaubrières — education department, 9 state schools (fictional authority)
- Sector
- Education department of a town of 19,400 inhabitants — 9 state schools (5 nursery, 4 primary), in-house school catering, before-school and after-school care, Wednesday and holiday clubs, local education plan adopted on 4 July 2025
- Headcount
- 11 staff in the education department, 5 of them on the school and out-of-school desk — 4 case officers and a service manager; the other 6 handle nursery assistants, buildings and educational projects, and the assistant does not touch that
- Public served
- 2,340 pupils and 1,760 families signed up for out-of-school services — 12,300 enquiries a year: 7,400 calls, 3,100 emails, 1,200 desk visits, 600 family-portal forms
- Order of magnitude
- 2,302 enrolment files a year — 412 school enrolments and 1,890 out-of-school registrations or changes; 96 catchment-waiver requests; 10 out-of-school billing runs from September to June, 17,600 invoices issued; 96 classes and 2,340 enrolment lists to prepare each September
- Tools already in place
- Family portal, childhood/family software (files, bookings, attendance records), revenue office and billing software, adopted catchment map, department mailbox and Microsoft Teams — the assistant connects to them read-only, nothing is replaced or migrated
- Who decides what
- The education service manager validates every invoice and every letter before it goes out; placements and waivers are decided by the department and the deputy mayor for education; means-test brackets and tariffs are set by resolution of the town council, as is the catchment area of each school, under article L. 212-7 of the French education code
- Room for improvement
- 2,368 calls out of 7,400 ring unanswered — 32%, 1,704 of them over the eight weeks of May and June; an email waits 8 days on average; a billing run ties up 3 case officers for 4 working days; and the family file had never been reconciled against attendance records and means-test brackets — 23 discrepancies were sitting in the Jules-Ferry school group alone
In Vaubrières, five staff handle enrolments, family enquiries and out-of-school billing for 1,760 families, with a spring peak when the enrolment campaign and the end of the school year overlap. The most repetitive questions — the price of a school meal, booking a meal, after-school opening hours, which school a street belongs to — take up more than three quarters of the flow, and the situations that genuinely need a case officer are the ones waiting behind them. The exchanges below cover one school year, from the reconciliation of the family file to the review presented to the deputy mayor for education. The assistant is hosted in France on an isolated resource, reads the childhood/family software and the attendance records without ever writing to them, and no invoice and no placement goes out without a named officer's validation.
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.
School administration assistant · hosted in France
I have reread your 12,300 enquiries for the school year and reconciled, family by family, your childhood/family file against the attendance records and the means-test brackets in force — the reconciliation the enrolment campaign never leaves time for.
What the count says: 11 topics cover 9,460 enquiries out of 12,300, i.e. 76.9% of the flow. Meal price and means-test bracket, out-of-school booking, before- and after-school hours, enrolment documents and calendar, Wednesday and holiday clubs, catchment school, menus and individual care plans, reading an invoice, cancelling a meal, catchment waivers, school transport. The 11 reference answers are written, sourced on your out-of-school service rules and on the resolutions of 16 December 2025, and dated — they are waiting for you.
What the three items you can check against your own logs are worth:
· Processing an enrolment takes 22 minutes end to end, 60% of it on checking documents, verifying the school catchment and data entry — 13 minutes 12.
· A routine answer to a family takes 9 minutes, 40% of it on finding the exact bracket, booking or opening hour — 3 minutes 36.
· Preparing an out-of-school billing run is 100% manual work: 4 working days for 3 case officers, i.e. 84 hours a month.
And the gap the reconciliation brought out, in the Jules-Ferry school group alone — 412 families: 23 discrepancies, never seen because nobody ever had the four days to look. 9 families billed on a means-test certificate more than twelve months old — 6 of which would have changed bracket —, 7 children recorded at a meal with no active booking, 4 invoices sent to a family whose withdrawal was already on record, 3 sibling groups without the discount the resolution provides for. In money: €214.80 you did not bill and €372.60 billed wrongly or to the wrong household.
The next step, and it takes half an hour: you reread the 23 lines and tell me, for each one, what you want done. The service manager signs off the version, and the 23 leave the file before the next invoice. school-service-flow_12300-enquiries-11-topics.pdf9,460 enquiries across 11 topics, the three items costed, 1,621 hours identified
⛓ Sourced · 12 months of enquiry logs, childhood/family file, attendance records, resolutions of 16 December 2025
What the count says: 11 topics cover 9,460 enquiries out of 12,300, i.e. 76.9% of the flow. Meal price and means-test bracket, out-of-school booking, before- and after-school hours, enrolment documents and calendar, Wednesday and holiday clubs, catchment school, menus and individual care plans, reading an invoice, cancelling a meal, catchment waivers, school transport. The 11 reference answers are written, sourced on your out-of-school service rules and on the resolutions of 16 December 2025, and dated — they are waiting for you.
What the three items you can check against your own logs are worth:
· Processing an enrolment takes 22 minutes end to end, 60% of it on checking documents, verifying the school catchment and data entry — 13 minutes 12.
· A routine answer to a family takes 9 minutes, 40% of it on finding the exact bracket, booking or opening hour — 3 minutes 36.
· Preparing an out-of-school billing run is 100% manual work: 4 working days for 3 case officers, i.e. 84 hours a month.
And the gap the reconciliation brought out, in the Jules-Ferry school group alone — 412 families: 23 discrepancies, never seen because nobody ever had the four days to look. 9 families billed on a means-test certificate more than twelve months old — 6 of which would have changed bracket —, 7 children recorded at a meal with no active booking, 4 invoices sent to a family whose withdrawal was already on record, 3 sibling groups without the discount the resolution provides for. In money: €214.80 you did not bill and €372.60 billed wrongly or to the wrong household.
The next step, and it takes half an hour: you reread the 23 lines and tell me, for each one, what you want done. The service manager signs off the version, and the 23 leave the file before the next invoice. school-service-flow_12300-enquiries-11-topics.pdf9,460 enquiries across 11 topics, the three items costed, 1,621 hours identified
⛓ Sourced · 12 months of enquiry logs, childhood/family file, attendance records, resolutions of 16 December 2025
23 discrepancies in one school — what does that mean across all nine? And above all: how do we avoid making the same ones next year?
Across your 1,760 families, the same reconciliation rule brings out 98 over the school year. In money: around €915 of revenue not billed and around €1,587 billed wrongly. The amount is not what matters most: each of those 98 lines is a family complaint waiting to happen, and a complaint costs 9 minutes plus the trust of a parent who receives an invoice they cannot understand.
What I have done on top, and what the campaign never leaves time for: I have written four control rules, in the language of your out-of-school service rules, and run them across your last 24 months of attendance records. For each one I give you how many alerts it would have produced, the share confirmed on examination, and what it would have let through — you choose on figures, not on a hunch:
· Rule A — an invoice calculated on a means-test certificate more than twelve months old on the day it is issued: 104 alerts over 24 months, 98 confirmed — 94.2%. The other 6 are certificates handed in at the desk and entered late, which is fixed at data entry.
· Rule B — a child recorded at a meal with no active booking that day: 62 alerts, 55 confirmed — 88.7%.
· Rule C — an invoice sent to a family whose withdrawal is recorded at an earlier date: 27 alerts, 27 confirmed — 100%.
And here is what those three rules let through, because you need to know before you sign: 18 sibling groups of two children or more did not receive the discount article 6 of your tariff resolution provides for, and none of the three sees them. So I wrote rule D — a family with two or more enrolled children whose invoice carries no sibling discount — and ran it over the same 24 months: 18 alerts, 17 confirmed.
The four together: 211 alerts over 24 months, 197 confirmed — 98 a year, exactly the figure the reconciliation produced — and they cover 197 of the 214 discrepancies found over the period, i.e. 92.0%.
Bringing a rule into force stays with the department: a rule only goes live once the service manager has approved it, and that is precisely what makes it defensible against a family disputing its invoice. I save you the writing and the measurement; the decision takes half an hour instead of a committee. billing-discrepancies_4-rules-tested-over-24-months.pdfThe 23 Jules-Ferry discrepancies in detail, 4 rules tested, 197 discrepancies out of 214 covered
⛓ Sourced · 24 months of attendance records, childhood/family file, out-of-school service rules, tariff resolution of 16 December 2025
What I have done on top, and what the campaign never leaves time for: I have written four control rules, in the language of your out-of-school service rules, and run them across your last 24 months of attendance records. For each one I give you how many alerts it would have produced, the share confirmed on examination, and what it would have let through — you choose on figures, not on a hunch:
· Rule A — an invoice calculated on a means-test certificate more than twelve months old on the day it is issued: 104 alerts over 24 months, 98 confirmed — 94.2%. The other 6 are certificates handed in at the desk and entered late, which is fixed at data entry.
· Rule B — a child recorded at a meal with no active booking that day: 62 alerts, 55 confirmed — 88.7%.
· Rule C — an invoice sent to a family whose withdrawal is recorded at an earlier date: 27 alerts, 27 confirmed — 100%.
And here is what those three rules let through, because you need to know before you sign: 18 sibling groups of two children or more did not receive the discount article 6 of your tariff resolution provides for, and none of the three sees them. So I wrote rule D — a family with two or more enrolled children whose invoice carries no sibling discount — and ran it over the same 24 months: 18 alerts, 17 confirmed.
The four together: 211 alerts over 24 months, 197 confirmed — 98 a year, exactly the figure the reconciliation produced — and they cover 197 of the 214 discrepancies found over the period, i.e. 92.0%.
Bringing a rule into force stays with the department: a rule only goes live once the service manager has approved it, and that is precisely what makes it defensible against a family disputing its invoice. I save you the writing and the measurement; the decision takes half an hour instead of a committee. billing-discrepancies_4-rules-tested-over-24-months.pdfThe 23 Jules-Ferry discrepancies in detail, 4 rules tested, 197 discrepancies out of 214 covered
⛓ Sourced · 24 months of attendance records, childhood/family file, out-of-school service rules, tariff resolution of 16 December 2025
We are talking about children. Identities, means-test data, separated-family situations, allergies: where does all that go?
Nowhere outside your walls, and that is something you verify rather than something I promise.
Where I run: on an isolated resource hosted in France, under French law, dedicated to Vaubrières and to nobody else — or on a machine belonging to the town if you prefer local inference, in which case nothing even leaves the network. No child's or family's data is passed to a foreign service: exposure to the Cloud Act and FISA 702 is reduced accordingly, without location alone ruling it out — it is documented for the configuration chosen. 0 items of data outside the European Union, and that is a fact of architecture, not a contract clause.
What I read, and what I cannot reach: I have read-only access to the childhood/family file, the attendance records, the catchment map and the school calendar. I have no write access to the billing software or to the family portal: I produce files and draft letters, your case officer imports them. Families' bank details are not open to me at all — I have no use for them in preparing an invoice, and article 5(1)(c) of the GDPR asks precisely that only what serves a purpose be exposed. Access is withdrawn on a word, and the withdrawal takes effect within the second.
The special case of health data, because it arises here: an individual care plan carries medical information. To serve a family and to build a rota I need only three items: whether a care plan exists, its validity date and the meal regime that follows from it. The medical content stays in the department's file and I do not read it — not out of caution, but because producing a menu has no use for it.
What you can show your data protection officer: every read is logged with its date, its purpose and the file concerned; every output carries the documents it is drawn from; and the record of processing activities is already written, legal basis by legal basis — public interest task for school enrolment and out-of-school billing, article 6(1)(e) of the GDPR.
The next step I suggest: a thirty-minute quarterly review where I show you the access rights actually used and those that served no purpose — an unused access right is an access right to close, and I bring you the list rather than asking you for it. sovereign-framework_hosting-access-traceability.pdfWhere children's data lives, who reads what, what is withdrawn on a word
✎ Framework · hosting architecture, access log, education department record of processing activities
Where I run: on an isolated resource hosted in France, under French law, dedicated to Vaubrières and to nobody else — or on a machine belonging to the town if you prefer local inference, in which case nothing even leaves the network. No child's or family's data is passed to a foreign service: exposure to the Cloud Act and FISA 702 is reduced accordingly, without location alone ruling it out — it is documented for the configuration chosen. 0 items of data outside the European Union, and that is a fact of architecture, not a contract clause.
What I read, and what I cannot reach: I have read-only access to the childhood/family file, the attendance records, the catchment map and the school calendar. I have no write access to the billing software or to the family portal: I produce files and draft letters, your case officer imports them. Families' bank details are not open to me at all — I have no use for them in preparing an invoice, and article 5(1)(c) of the GDPR asks precisely that only what serves a purpose be exposed. Access is withdrawn on a word, and the withdrawal takes effect within the second.
The special case of health data, because it arises here: an individual care plan carries medical information. To serve a family and to build a rota I need only three items: whether a care plan exists, its validity date and the meal regime that follows from it. The medical content stays in the department's file and I do not read it — not out of caution, but because producing a menu has no use for it.
What you can show your data protection officer: every read is logged with its date, its purpose and the file concerned; every output carries the documents it is drawn from; and the record of processing activities is already written, legal basis by legal basis — public interest task for school enrolment and out-of-school billing, article 6(1)(e) of the GDPR.
The next step I suggest: a thirty-minute quarterly review where I show you the access rights actually used and those that served no purpose — an unused access right is an access right to close, and I bring you the list rather than asking you for it. sovereign-framework_hosting-access-traceability.pdfWhere children's data lives, who reads what, what is withdrawn on a word
✎ Framework · hosting architecture, access log, education department record of processing activities
Check this nursery enrolment file for September.
File checked, in forty seconds. Documents present: family record book, proof of address less than three months old, and the certificate attesting to the eleven compulsory vaccinations for children born since 1 January 2018, under article L. 3111-2 of the French public health code. The address does fall within the catchment of Jules-Ferry school, as adopted by the catchment resolution of 16 December 2025, taken under article L. 212-7 of the education code — I quote the article and the resolution, because a placement that gives its reasons is a placement that holds.
One document is missing, and only one: the court order setting the child's residence, mentioned by the family in the form but not attached. The letter requesting it is written, with the reason, the deadline, the ways of submitting it — family portal, desk or email — and a statement that the place is held meanwhile. That last point is what prevents next week's anxious phone call.
What I now do on submission, rather than three weeks later: across your 2,302 files from last year rerun against this rule, 386 were incomplete — 16.8%. A document missing in 194 cases, proof of address older than three months in 108 cases, and in 84 cases an address outside the catchment of the school requested — those 84 deserve a mention: they are 84 families who found out three weeks too late that they needed to file a waiver request, when they could be told the same day.
What I read and what I keep: I take the name, the address, the date of the document and the family relationship. The rest of the supporting document is of no interest to me and is not retained — a tax notice carries far more than an enrolment needs.
What that is worth over the year: your 2,302 files go from 13 minutes 12 of checking and entry to 2 minutes 12 — 60% of the enrolment time down to 10%, i.e. 422 hours returned to the department. And the processing time for a file goes from 18 days to 5, because today's three weeks are three weeks of documents going back and forth.
Nothing is enrolled or placed: the file goes to decision complete, sourced and dated, and it is an officer who enrols the child. enrolments-and-waivers_nursery-file-and-96-requests.pdfThe nursery file document by document, the 386 incomplete files caught on submission, the 96 waivers sorted
⛓ Sourced · family file submitted on 14 April, catchment map adopted on 16 December 2025, 2,302 files from the year rerun against the control rule
One document is missing, and only one: the court order setting the child's residence, mentioned by the family in the form but not attached. The letter requesting it is written, with the reason, the deadline, the ways of submitting it — family portal, desk or email — and a statement that the place is held meanwhile. That last point is what prevents next week's anxious phone call.
What I now do on submission, rather than three weeks later: across your 2,302 files from last year rerun against this rule, 386 were incomplete — 16.8%. A document missing in 194 cases, proof of address older than three months in 108 cases, and in 84 cases an address outside the catchment of the school requested — those 84 deserve a mention: they are 84 families who found out three weeks too late that they needed to file a waiver request, when they could be told the same day.
What I read and what I keep: I take the name, the address, the date of the document and the family relationship. The rest of the supporting document is of no interest to me and is not retained — a tax notice carries far more than an enrolment needs.
What that is worth over the year: your 2,302 files go from 13 minutes 12 of checking and entry to 2 minutes 12 — 60% of the enrolment time down to 10%, i.e. 422 hours returned to the department. And the processing time for a file goes from 18 days to 5, because today's three weeks are three weeks of documents going back and forth.
Nothing is enrolled or placed: the file goes to decision complete, sourced and dated, and it is an officer who enrols the child. enrolments-and-waivers_nursery-file-and-96-requests.pdfThe nursery file document by document, the 386 incomplete files caught on submission, the 96 waivers sorted
⛓ Sourced · family file submitted on 14 April, catchment map adopted on 16 December 2025, 2,302 files from the year rerun against the control rule
The real problem is the phone. In May and June we stop picking up. One family in three gets nothing.
2,368 calls out of 7,400 ring unanswered — 32%, and 1,704 of them fall in the eight weeks of May and June. This is not a quality-of-service problem, it is a timing problem: your 4 case officers are needed six at a time between 8.30 and 10.
What I take, and what I leave you: I answer every call, I state in my first sentence that I am an artificial intelligence — article 50(1) of the European AI regulation has required this since 2 August 2026, and the family can ask for a human officer at any time — and I handle end to end the 11 topics whose answers are approved and dated. Anything outside those 11 topics goes to a case officer with the file already assembled: the family, the enrolled children, the current means-test bracket and its validity date, the month's bookings, the last letter sent, and the question asked word for word. Your case officer picks up knowing, instead of picking up searching.
The arithmetic, and it is yours: the 11 topics account for 76.9% of the flow; 2,368 unanswered calls fall to 148, i.e. 2,220 more families who get their answer — 1,612 of them in the evening, at the weekend or during the holidays, when your desk is closed and a mother working shifts can finally call. And a routine answer goes from 3 minutes 36 to 54 seconds — 40% of the time down to 10%, i.e. 425 hours returned across 9,460 enquiries.
And I reach them on the channels they already have: WhatsApp Business, the site chat and email, with no account to create and no app to install. This is equal access as much as convenience: the family portal form does not reach families without a computer, and those are often the ones whose means-test bracket opens the lowest tariffs — a holiday club place that is never requested is an entitlement that never happens. Your own staff talk to me from Microsoft Teams, Slack or their mailbox, without changing tools. Email, which waits 8 days today, goes back to 1 day.
The figure that does not flatter me, and I publish it: across the 2,365 enquiries of the first quarter, I attached 61 families to the wrong catchment school — 2.6%. All of them concerned the 4 streets redrawn by the catchment resolution of 3 February 2026: I was reading the map in force on the day of the enquiry, not the map applicable to the school year requested. That is fixed: I now read the map applicable to the September concerned. In the second quarter, 9 errors out of 2,365 — 0.4%. I suggest continuing to publish that rate every quarter: an assistant whose errors are not measured is an assistant that cannot be corrected. family-channels_multichannel-desk-and-plain-language.pdfThe 11 topics handled end to end, how the rest is routed, the published error rate
⛓ Sourced · 12 months of switchboard logs, assistant routing log, catchment resolutions of 16 December 2025 and 3 February 2026
What I take, and what I leave you: I answer every call, I state in my first sentence that I am an artificial intelligence — article 50(1) of the European AI regulation has required this since 2 August 2026, and the family can ask for a human officer at any time — and I handle end to end the 11 topics whose answers are approved and dated. Anything outside those 11 topics goes to a case officer with the file already assembled: the family, the enrolled children, the current means-test bracket and its validity date, the month's bookings, the last letter sent, and the question asked word for word. Your case officer picks up knowing, instead of picking up searching.
The arithmetic, and it is yours: the 11 topics account for 76.9% of the flow; 2,368 unanswered calls fall to 148, i.e. 2,220 more families who get their answer — 1,612 of them in the evening, at the weekend or during the holidays, when your desk is closed and a mother working shifts can finally call. And a routine answer goes from 3 minutes 36 to 54 seconds — 40% of the time down to 10%, i.e. 425 hours returned across 9,460 enquiries.
And I reach them on the channels they already have: WhatsApp Business, the site chat and email, with no account to create and no app to install. This is equal access as much as convenience: the family portal form does not reach families without a computer, and those are often the ones whose means-test bracket opens the lowest tariffs — a holiday club place that is never requested is an entitlement that never happens. Your own staff talk to me from Microsoft Teams, Slack or their mailbox, without changing tools. Email, which waits 8 days today, goes back to 1 day.
The figure that does not flatter me, and I publish it: across the 2,365 enquiries of the first quarter, I attached 61 families to the wrong catchment school — 2.6%. All of them concerned the 4 streets redrawn by the catchment resolution of 3 February 2026: I was reading the map in force on the day of the enquiry, not the map applicable to the school year requested. That is fixed: I now read the map applicable to the September concerned. In the second quarter, 9 errors out of 2,365 — 0.4%. I suggest continuing to publish that rate every quarter: an assistant whose errors are not measured is an assistant that cannot be corrected. family-channels_multichannel-desk-and-plain-language.pdfThe 11 topics handled end to end, how the rest is routed, the published error rate
⛓ Sourced · 12 months of switchboard logs, assistant routing log, catchment resolutions of 16 December 2025 and 3 February 2026
And the 96 catchment-waiver requests? The panel sits in June and we spend two weeks preparing the files.
The 96 requests are investigated, sorted and ready for the panel — and the decision stays entirely with the deputy mayor and the department.
What I have done on each one: documents checked, address matched against the catchment map applicable to the September requested, reason matched to its rule, and roll numbers for the school and year group requested, current as at the day of the panel — that last figure is always the one missing at the moment of decision, and it is never in the paper file.
The sorting, because the two regimes are not alike:
· 62 requests are internal to Vaubrières — changing school within the town. There is no national rule here: the catchment of each school is set by your town council (article L. 212-7 of the education code), and the grounds for exception are those of your own resolution of 16 December 2025. So I have matched them to YOUR grid, article by article — sibling already at the school 24, care by a third party living in another catchment 17, continuity of schooling 12, other grounds 9. A rule of caution is not a rule of law: I quote your text, dated, and not a custom.
· 34 requests involve another municipality, in one direction or the other. There, article L. 212-8 of the education code matters: it sets out the cases in which the municipality of residence must contribute to schooling costs — notably the parents' work commitments where their own municipality provides neither catering nor childcare, the child's state of health, and a brother or sister enrolled in the same municipality. 21 of the 34 fall within one of those cases; for the other 13, the contribution requires an agreement between the two municipalities, and I have drafted the 13 letters.
What the panel receives: one file per request, two pages, the same template — the request, the documents, the applicable rule quoted with its source, the roll numbers, and the comparable decisions of your last three panels, because a panel that contradicts itself from one year to the next is a panel that gets challenged.
What I do not pronounce, and this is not caution on my part: placing a child in a school is a decision that belongs to you. If you ever wanted to automate it, it would be possible but regulated — assigning a person to an educational institution falls under point 3 of Annex III to the European AI regulation, that is, the high-risk regime, with the obligations that come with it. I bring you the conditions to be met should you decide to; as things stand, I prepare and you sign, and that is the arrangement that costs you least.
What it gives you back: the two weeks of preparation become half a day of reading, and the panel sits on files that are identical in form. enrolments-and-waivers_nursery-file-and-96-requests.pdfThe 96 requests sorted by regime and by ground, the panel file template
⛓ Sourced · 96 waiver requests from the campaign, resolution of 16 December 2025, article L. 212-8 of the education code, roll numbers by school and year group
What I have done on each one: documents checked, address matched against the catchment map applicable to the September requested, reason matched to its rule, and roll numbers for the school and year group requested, current as at the day of the panel — that last figure is always the one missing at the moment of decision, and it is never in the paper file.
The sorting, because the two regimes are not alike:
· 62 requests are internal to Vaubrières — changing school within the town. There is no national rule here: the catchment of each school is set by your town council (article L. 212-7 of the education code), and the grounds for exception are those of your own resolution of 16 December 2025. So I have matched them to YOUR grid, article by article — sibling already at the school 24, care by a third party living in another catchment 17, continuity of schooling 12, other grounds 9. A rule of caution is not a rule of law: I quote your text, dated, and not a custom.
· 34 requests involve another municipality, in one direction or the other. There, article L. 212-8 of the education code matters: it sets out the cases in which the municipality of residence must contribute to schooling costs — notably the parents' work commitments where their own municipality provides neither catering nor childcare, the child's state of health, and a brother or sister enrolled in the same municipality. 21 of the 34 fall within one of those cases; for the other 13, the contribution requires an agreement between the two municipalities, and I have drafted the 13 letters.
What the panel receives: one file per request, two pages, the same template — the request, the documents, the applicable rule quoted with its source, the roll numbers, and the comparable decisions of your last three panels, because a panel that contradicts itself from one year to the next is a panel that gets challenged.
What I do not pronounce, and this is not caution on my part: placing a child in a school is a decision that belongs to you. If you ever wanted to automate it, it would be possible but regulated — assigning a person to an educational institution falls under point 3 of Annex III to the European AI regulation, that is, the high-risk regime, with the obligations that come with it. I bring you the conditions to be met should you decide to; as things stand, I prepare and you sign, and that is the arrangement that costs you least.
What it gives you back: the two weeks of preparation become half a day of reading, and the panel sits on files that are identical in form. enrolments-and-waivers_nursery-file-and-96-requests.pdfThe 96 requests sorted by regime and by ground, the panel file template
⛓ Sourced · 96 waiver requests from the campaign, resolution of 16 December 2025, article L. 212-8 of the education code, roll numbers by school and year group
Prepare the May school-meal invoices, with the means-test brackets.
Billing prepared. May attendance reconciled against bookings, tariffs applied according to the means-test brackets in force — the six brackets adopted by the resolution of 16 December 2025, with the sibling discount of its article 6 — twelve discrepancies flagged: justified absences to be checked. Invoices generated from your own templates. Nothing goes out without your validation.
The run in detail: 1,760 families, 1,748 invoices ready, 12 lines held for checking — a medical certificate submitted after bookings closed in 7 cases, a school trip not reflected in bookings in 3 cases, a class closure in 2 cases. Those twelve do not go out as invoices, they go to checking, with the document already attached where the family had submitted one.
What each line carries, and this is the rule I suggest we hold: every billed line traces back to a time-stamped attendance record, to a booking, and to a means-test bracket still valid on the day of issue. A line missing any one of the three does not go out. That is what lets you, faced with a family that disputes it, produce the day, the time of attendance, the booking and the article of the resolution — instead of a total.
The variance against April is −3.1%, and it is fully explained: two fewer service days for public holidays and 26 end-of-year withdrawals. I give you the 26 movements, so you will not have to hunt for where the variance comes from — it is the first question a deputy mayor reading a dashboard asks.
What that is worth: 84 hours per run today, 4 working days for three case officers. Afterwards: 16 hours 48 of checking and validation, i.e. 20% of the current time — under one working day for three. 67 hours returned per run, 672 hours over the year's ten runs.
The covering letters are ready too — three templates: first invoice after enrolment, invoice up by more than 30% after a change of bracket, invoice carrying exceptional meals. Each explains the calculation in plain language, short sentences, one idea per sentence: an invoice that is understood is a call that never happens.
The next step I suggest: opening the same preparation on the Wednesday holiday club, where bookings change most often. That is where your twelve monthly discrepancies are most at risk of becoming thirty. out-of-school-billing_may-1760-families.pdf1,748 invoices ready, the 12 discrepancies in detail, the three letter templates
✎ Action · billing prepared — the education service manager validates before sending · tariff resolution of 16 December 2025
The run in detail: 1,760 families, 1,748 invoices ready, 12 lines held for checking — a medical certificate submitted after bookings closed in 7 cases, a school trip not reflected in bookings in 3 cases, a class closure in 2 cases. Those twelve do not go out as invoices, they go to checking, with the document already attached where the family had submitted one.
What each line carries, and this is the rule I suggest we hold: every billed line traces back to a time-stamped attendance record, to a booking, and to a means-test bracket still valid on the day of issue. A line missing any one of the three does not go out. That is what lets you, faced with a family that disputes it, produce the day, the time of attendance, the booking and the article of the resolution — instead of a total.
The variance against April is −3.1%, and it is fully explained: two fewer service days for public holidays and 26 end-of-year withdrawals. I give you the 26 movements, so you will not have to hunt for where the variance comes from — it is the first question a deputy mayor reading a dashboard asks.
What that is worth: 84 hours per run today, 4 working days for three case officers. Afterwards: 16 hours 48 of checking and validation, i.e. 20% of the current time — under one working day for three. 67 hours returned per run, 672 hours over the year's ten runs.
The covering letters are ready too — three templates: first invoice after enrolment, invoice up by more than 30% after a change of bracket, invoice carrying exceptional meals. Each explains the calculation in plain language, short sentences, one idea per sentence: an invoice that is understood is a call that never happens.
The next step I suggest: opening the same preparation on the Wednesday holiday club, where bookings change most often. That is where your twelve monthly discrepancies are most at risk of becoming thirty. out-of-school-billing_may-1760-families.pdf1,748 invoices ready, the 12 discrepancies in detail, the three letter templates
✎ Action · billing prepared — the education service manager validates before sending · tariff resolution of 16 December 2025
The other big job is September: the enrolment lists by school and the out-of-school rotas take us three weeks.
The September lists and rotas are prepared, and I have kept for you the only part that is yours: the judgement calls.
What I produce, from validated enrolments: the list of enrolled pupils by school and year group — 2,340 pupils, 9 schools —, projected roll numbers compared with last year school by school, and the 4 year groups where the gap exceeds 10%, because those are the ones you will discuss with the schools inspectorate. The list of children subject to compulsory education that the mayor must keep is produced in the same pass, current and dated.
What stays with the head teacher, and this is not a division I have invented: allocating pupils between classes is their responsibility, not the town's. So I send them a clean, complete list, not a class composition — and that is exactly what they need on 25 August.
The out-of-school rotas: 36 weeks, 9 schools, morning, midday and evening. I build them on actual bookings, and I set the supervision ratios against each session: one leader for ten children under six and one for fourteen above, with the relaxed ratios of one for fourteen and one for eighteen that your local education plan adopted on 4 July 2025 makes available. Result: 7 sessions out of 972 come out under-supervised against the bookings — all on Thursday evening, in the two schools where supervised study and after-school care overlap. I flag them in July and not in September, and for each one I give you how many leaders are missing.
What that is worth: 128 hours today, 26 hours afterwards — 102 hours returned each September, and above all three weeks of calendar down to four days, which changes the date on which you can recruit the leaders you are short of.
The next step I suggest: replaying the rotas in mid-September against the bookings actually observed, and telling you where the gap between forecast and actual exceeds 15% — that is where the supervision hours paid for nothing sit, and nobody has time to go looking for them. lists-and-rotas_september-9-schools-96-classes.pdfRoll numbers by school and year group, 972 sessions checked, the 7 under-supervised sessions
⛓ Sourced · enrolments validated at 30 June, out-of-school bookings for the past year, local education plan of 4 July 2025, article R. 227-16 of the social action and families code
What I produce, from validated enrolments: the list of enrolled pupils by school and year group — 2,340 pupils, 9 schools —, projected roll numbers compared with last year school by school, and the 4 year groups where the gap exceeds 10%, because those are the ones you will discuss with the schools inspectorate. The list of children subject to compulsory education that the mayor must keep is produced in the same pass, current and dated.
What stays with the head teacher, and this is not a division I have invented: allocating pupils between classes is their responsibility, not the town's. So I send them a clean, complete list, not a class composition — and that is exactly what they need on 25 August.
The out-of-school rotas: 36 weeks, 9 schools, morning, midday and evening. I build them on actual bookings, and I set the supervision ratios against each session: one leader for ten children under six and one for fourteen above, with the relaxed ratios of one for fourteen and one for eighteen that your local education plan adopted on 4 July 2025 makes available. Result: 7 sessions out of 972 come out under-supervised against the bookings — all on Thursday evening, in the two schools where supervised study and after-school care overlap. I flag them in July and not in September, and for each one I give you how many leaders are missing.
What that is worth: 128 hours today, 26 hours afterwards — 102 hours returned each September, and above all three weeks of calendar down to four days, which changes the date on which you can recruit the leaders you are short of.
The next step I suggest: replaying the rotas in mid-September against the bookings actually observed, and telling you where the gap between forecast and actual exceeds 15% — that is where the supervision hours paid for nothing sit, and nobody has time to go looking for them. lists-and-rotas_september-9-schools-96-classes.pdfRoll numbers by school and year group, 972 sessions checked, the 7 under-supervised sessions
⛓ Sourced · enrolments validated at 30 June, out-of-school bookings for the past year, local education plan of 4 July 2025, article R. 227-16 of the social action and families code
How do we bring your four rules in? And what if one of them starts flagging nonsense?
One at a time, each with its entry figure, and none starts without your signature.
The order I recommend, and the arithmetic behind it: rule C first — 27 alerts over 24 months, 100% confirmed, so no examination time wasted; then A — 104 alerts, 94.2% confirmed, and it is the rule that hits families hardest in the pocket, since an out-of-date certificate makes a family whose circumstances have changed pay last year's tariff; then D, then B. I advise against switching them all on in the same month, and I cost it: the four together would produce 41 alerts in the first run, i.e. around 7 hours of examination for your case officers, in the middle of the enrolment campaign. One per run is under 2 hours each time, and you keep control of what you look at.
What I watch for you, without being asked: the confirmed share of each rule, run after run. A rule that drops below 80% confirmation is a rule that makes you examine families for nothing: I warn you in the very run concerned, with the tightened version already written and already run against the history, as I did for rule B — its first drafting flagged every attendance without a booking and produced 148 alerts for 55 confirmed (37.2%), because it counted the emergency meals provided for in article 4 of your service rules; the tightened version, which excludes emergency meals declared the same morning, produces 62 for 55 confirmed — the 55 genuine ones kept, 86 families spared being looked at for nothing. It is the tightened version I put to you, not the first one.
And where you need to write me a mandate, because it commits you: sending an invoice, enrolling a child, granting a waiver or removing a child from the roll are acts of the municipality. These are not acts I refuse — they are acts I carry out as soon as the mandate is written: named scope, stated ceiling, review date, and withdrawal on a word. The model mandate is drafted, with three scopes to choose from — from the most cautious (nothing goes out without line-by-line validation) to the broadest (invoices with no discrepancy go out on their own, the 12 held lines wait). You choose the setting, and you can move it in either direction at any time.
And withdrawal is as simple as going live: a rule stops on a word, within the second, and the lines it had held go back into billing with the reason and the date of the withdrawal. Nothing is blocked for good, nothing disappears. billing-discrepancies_4-rules-tested-over-24-months.pdfThe go-live schedule, the tightened version of rule B, the three-setting mandate
⛓ Sourced · 24 months of attendance records, comparative measurement of the two draftings of rule B, out-of-school service rules
The order I recommend, and the arithmetic behind it: rule C first — 27 alerts over 24 months, 100% confirmed, so no examination time wasted; then A — 104 alerts, 94.2% confirmed, and it is the rule that hits families hardest in the pocket, since an out-of-date certificate makes a family whose circumstances have changed pay last year's tariff; then D, then B. I advise against switching them all on in the same month, and I cost it: the four together would produce 41 alerts in the first run, i.e. around 7 hours of examination for your case officers, in the middle of the enrolment campaign. One per run is under 2 hours each time, and you keep control of what you look at.
What I watch for you, without being asked: the confirmed share of each rule, run after run. A rule that drops below 80% confirmation is a rule that makes you examine families for nothing: I warn you in the very run concerned, with the tightened version already written and already run against the history, as I did for rule B — its first drafting flagged every attendance without a booking and produced 148 alerts for 55 confirmed (37.2%), because it counted the emergency meals provided for in article 4 of your service rules; the tightened version, which excludes emergency meals declared the same morning, produces 62 for 55 confirmed — the 55 genuine ones kept, 86 families spared being looked at for nothing. It is the tightened version I put to you, not the first one.
And where you need to write me a mandate, because it commits you: sending an invoice, enrolling a child, granting a waiver or removing a child from the roll are acts of the municipality. These are not acts I refuse — they are acts I carry out as soon as the mandate is written: named scope, stated ceiling, review date, and withdrawal on a word. The model mandate is drafted, with three scopes to choose from — from the most cautious (nothing goes out without line-by-line validation) to the broadest (invoices with no discrepancy go out on their own, the 12 held lines wait). You choose the setting, and you can move it in either direction at any time.
And withdrawal is as simple as going live: a rule stops on a word, within the second, and the lines it had held go back into billing with the reason and the date of the withdrawal. Nothing is blocked for good, nothing disappears. billing-discrepancies_4-rules-tested-over-24-months.pdfThe go-live schedule, the tightened version of rule B, the three-setting mandate
⛓ Sourced · 24 months of attendance records, comparative measurement of the two draftings of rule B, out-of-school service rules
The deputy mayor for education wants a twelve-month review for the schools committee. What do I present?
Four figures, and each one can be checked against your own logs — the only way to stand up before a committee.
· 1,621 hours returned to the department over the school year, item by item: 422 h on processing enrolments, 425 h on routine family answers, 672 h on the ten billing runs, 102 h on September lists and rotas. At 1,607 hours to a working year, that is more than a working year returned to your five staff — more than forty-six weeks at 35 hours. No post cut, no post created: it is time returned to the desk, to the families who need an officer in front of them, and to the difficult files that were waiting behind the tariff questions.
· 2,368 unanswered calls down to 148, email from 8 days to 1 day, and the processing time for an enrolment file from 18 days to 5.
· 98 billing discrepancies taken out of the file over the year, where the reconciliation was never done — around €915 of revenue restored and around €1,587 that did not go out wrongly, and above all 98 incomprehensible invoices that families did not receive.
· 0 placements made without an officer, 0 waivers granted by the machine, 0 invoices issued without a named validation, 0 items of data outside the European Union.
What I bring you on top, and what waits for you every year: the indicators the schools committee asks for — roll numbers by school and year group, out-of-school occupancy, average enrolment processing time, share of waivers granted by ground — are extracted, dated, with the query that produces them, so that a councillor who asks where a figure comes from gets the answer in the meeting. The review is still written and presented by you: it is an act of the department, not a machine output.
The next step I suggest for the coming year: the heaviest item left is the spring enrolment campaign — 412 files over six weeks. I suggest measuring, next year, the gap between the 4 schools where the document request goes out on the day of submission and the other 5, on the single criterion of time to a complete file. It is a protocol, not a promise: if the gap is nil, you will hear it from me. year-review_1621-hours-item-by-item.pdfThe 1,621 hours in detail, the turnaround times held, the schools committee indicators
⛓ Sourced · 12 months of department logs, childhood/family file, attendance records, waiver panel files
· 1,621 hours returned to the department over the school year, item by item: 422 h on processing enrolments, 425 h on routine family answers, 672 h on the ten billing runs, 102 h on September lists and rotas. At 1,607 hours to a working year, that is more than a working year returned to your five staff — more than forty-six weeks at 35 hours. No post cut, no post created: it is time returned to the desk, to the families who need an officer in front of them, and to the difficult files that were waiting behind the tariff questions.
· 2,368 unanswered calls down to 148, email from 8 days to 1 day, and the processing time for an enrolment file from 18 days to 5.
· 98 billing discrepancies taken out of the file over the year, where the reconciliation was never done — around €915 of revenue restored and around €1,587 that did not go out wrongly, and above all 98 incomprehensible invoices that families did not receive.
· 0 placements made without an officer, 0 waivers granted by the machine, 0 invoices issued without a named validation, 0 items of data outside the European Union.
What I bring you on top, and what waits for you every year: the indicators the schools committee asks for — roll numbers by school and year group, out-of-school occupancy, average enrolment processing time, share of waivers granted by ground — are extracted, dated, with the query that produces them, so that a councillor who asks where a figure comes from gets the answer in the meeting. The review is still written and presented by you: it is an act of the department, not a machine output.
The next step I suggest for the coming year: the heaviest item left is the spring enrolment campaign — 412 files over six weeks. I suggest measuring, next year, the gap between the 4 schools where the document request goes out on the day of submission and the other 5, on the single criterion of time to a complete file. It is a protocol, not a promise: if the gap is nil, you will hear it from me. year-review_1621-hours-item-by-item.pdfThe 1,621 hours in detail, the turnaround times held, the schools committee indicators
⛓ Sourced · 12 months of department logs, childhood/family file, attendance records, waiver panel files
In practical terms, what does the assistant do without asking us? That is the question the committee will put.
Three actions, not one more, and all three can be undone.
· I acknowledge every enrolment or booking request within the minute, with the list of documents received, those missing, and the deadline for submitting them. And the reverse is true as well: if the family submits the document the next day, the scheduled reminder cancels itself within the second and the file goes back into the queue — a family that has done what was asked of it does not get a chasing letter; that is the minimum respect it is owed.
· I hold for checking any invoice line that triggers a rule in service. And the reverse is true as well: the case officer clears it on a word, the line goes back into billing, with the reason and the date of the clearance — which gives you, at the next run, the list of the most frequent reasons, and therefore the rules to tighten.
· I send the closure or deadline reminder to the families concerned only, the day before, on the calendar set by the department. It can be withdrawn on a word as long as it has not gone out, and a family that asks to stop receiving it is removed within the second — just as it is put back within the second if it asks again. A withdrawal is not a door closed for life.
Everything else waits for a named decision: no enrolment is made, no placement or waiver is granted, no invoice is issued, no child is removed from the roll, no means-test bracket is changed, no discount is allowed.
A word on a measurement I can produce and would advise you not to install as it stands: the number of files handled per case officer. I know how to calculate it, and I will produce it if you ask — an employer's power of oversight is recognised, subject to three cumulative conditions, as the CNIL sets them out in its guidance on monitoring employees' activity: proportionality of the indicator to the aim pursued, prior information of staff, and consultation of the local staff committee before implementation. My reservation is not legal, it is mechanical: a per-officer counter becomes a target, the target distorts triage, and the long files — a family in payment difficulty, a disputed waiver, a separation under way — get pushed back in favour of the short ones. You would lose the instrument along with the measurement, and you would lose it precisely on the families who most need the service. What I suggest instead, and it is already prepared: measurement by QUEUE — turnaround, backlog, rework rate — which tells you where things stick without telling you who. One exception, and it is not really one: whoever validates an invoice or makes an enrolment is named and dated. A signature is not a counter. automatic-actions_three-acts-and-their-withdrawal.pdfThe 3 actions, how each is undone, what stays with a human decision
✎ Framework · automatic action settings, withdrawal log, conditions for implementing an individual indicator
· I acknowledge every enrolment or booking request within the minute, with the list of documents received, those missing, and the deadline for submitting them. And the reverse is true as well: if the family submits the document the next day, the scheduled reminder cancels itself within the second and the file goes back into the queue — a family that has done what was asked of it does not get a chasing letter; that is the minimum respect it is owed.
· I hold for checking any invoice line that triggers a rule in service. And the reverse is true as well: the case officer clears it on a word, the line goes back into billing, with the reason and the date of the clearance — which gives you, at the next run, the list of the most frequent reasons, and therefore the rules to tighten.
· I send the closure or deadline reminder to the families concerned only, the day before, on the calendar set by the department. It can be withdrawn on a word as long as it has not gone out, and a family that asks to stop receiving it is removed within the second — just as it is put back within the second if it asks again. A withdrawal is not a door closed for life.
Everything else waits for a named decision: no enrolment is made, no placement or waiver is granted, no invoice is issued, no child is removed from the roll, no means-test bracket is changed, no discount is allowed.
A word on a measurement I can produce and would advise you not to install as it stands: the number of files handled per case officer. I know how to calculate it, and I will produce it if you ask — an employer's power of oversight is recognised, subject to three cumulative conditions, as the CNIL sets them out in its guidance on monitoring employees' activity: proportionality of the indicator to the aim pursued, prior information of staff, and consultation of the local staff committee before implementation. My reservation is not legal, it is mechanical: a per-officer counter becomes a target, the target distorts triage, and the long files — a family in payment difficulty, a disputed waiver, a separation under way — get pushed back in favour of the short ones. You would lose the instrument along with the measurement, and you would lose it precisely on the families who most need the service. What I suggest instead, and it is already prepared: measurement by QUEUE — turnaround, backlog, rework rate — which tells you where things stick without telling you who. One exception, and it is not really one: whoever validates an invoice or makes an enrolment is named and dated. A signature is not a counter. automatic-actions_three-acts-and-their-withdrawal.pdfThe 3 actions, how each is undone, what stays with a human decision
✎ Framework · automatic action settings, withdrawal log, conditions for implementing an individual indicator
And the day a family disputes its invoice saying the machine decided?
On that day you produce three items and the dispute settles on facts.
One — the line itself: the day, the time of the attendance record, the matching booking, the means-test bracket applied with the date of the certificate behind it, plus the article of the resolution of 16 December 2025 that sets the tariff. Every billed line traces back to a time-stamped attendance record, a booking and a bracket still valid: that is the rule we have held since the first run, and it is what makes the invoice defensible.
Two — who decided: the name of the officer who validated the run, the date and the time of validation. No invoice has been issued by the machine and no enrolment has been made by it: I prepare, an officer decides. Over the year, 0 invoices issued without a named validation and 0 placements made without an officer — and the log shows it line by line.
Three — what the family knew, and when: I stated that I was an artificial intelligence in the first sentence of every exchange, in accordance with article 50(1) of the European AI regulation, applicable since 2 August 2026, and the family could ask for a human officer at any time — 486 did so over the year, and all 486 got one.
And if the family wants to see what you hold on their child: the access file is produced in one minute — enrolments, bookings, attendance records, invoices, letters, and the log of the reads I made of the file with their purpose. That is the right of access under article 15 of the GDPR, and the usual difficulty is assembling the material: it is already assembled. On a child's file the request comes from a holder of parental responsibility, and the log records which one was served and on what date — that is the first point a separated parent checks.
The next step I suggest: an annual review with your data protection officer, thirty minutes, where I bring you the access rights that served no purpose over the year and the files whose retention period has expired. You decide what to close and erase; I bring you the list rather than waiting to be asked. sovereign-framework_hosting-access-traceability.pdfWhat you produce on the day of a dispute: the line, the validator, the disclosure
✎ Framework · validation log, AI disclosure log, record of processing activities, resolution of 16 December 2025
One — the line itself: the day, the time of the attendance record, the matching booking, the means-test bracket applied with the date of the certificate behind it, plus the article of the resolution of 16 December 2025 that sets the tariff. Every billed line traces back to a time-stamped attendance record, a booking and a bracket still valid: that is the rule we have held since the first run, and it is what makes the invoice defensible.
Two — who decided: the name of the officer who validated the run, the date and the time of validation. No invoice has been issued by the machine and no enrolment has been made by it: I prepare, an officer decides. Over the year, 0 invoices issued without a named validation and 0 placements made without an officer — and the log shows it line by line.
Three — what the family knew, and when: I stated that I was an artificial intelligence in the first sentence of every exchange, in accordance with article 50(1) of the European AI regulation, applicable since 2 August 2026, and the family could ask for a human officer at any time — 486 did so over the year, and all 486 got one.
And if the family wants to see what you hold on their child: the access file is produced in one minute — enrolments, bookings, attendance records, invoices, letters, and the log of the reads I made of the file with their purpose. That is the right of access under article 15 of the GDPR, and the usual difficulty is assembling the material: it is already assembled. On a child's file the request comes from a holder of parental responsibility, and the log records which one was served and on what date — that is the first point a separated parent checks.
The next step I suggest: an annual review with your data protection officer, thirty minutes, where I bring you the access rights that served no purpose over the year and the files whose retention period has expired. You decide what to close and erase; I bring you the list rather than waiting to be asked. sovereign-framework_hosting-access-traceability.pdfWhat you produce on the day of a dispute: the line, the validator, the disclosure
✎ Framework · validation log, AI disclosure log, record of processing activities, resolution of 16 December 2025
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 school administration department
Each use corresponds to an agent we deploy. All work in support, subject to the officer's approval.
Included in your agent
The 5 capabilities essential to this promise are included, at no extra cost.
From 880 € incl. VAT / month
School & out-of-school enrolment
Handling enrolments, checking documents and catchment, tracking the lists.
Answers to families
Answer everyday questions (school meals, holiday club, means-tested rates) and direct people.
Lists & timetables
Preparing class lists, numbers and out-of-school timetables, under the officer's control.
Means-tested invoicing
Prepared calculation of out-of-school invoicing and the notices to families, for approval before sending.
Catchment exemptions
Prepared assessment of exemption requests; the decision stays with the department and the elected member concerned.
Controls and safeguards
These 4 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
Protect pupils’ data and prevent substitution or cheating uses
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 school department win back?
By automating enrolment, replies to families and invoicing, an authority can aim for a clear reduction in time spent on repetitive tasks — reinvested in the quality of welcome for children and families.
Handling a school enrolment
Answering a family's everyday question
Preparing the month's out-of-school invoicing
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 school administration agent (enrolment, replies to families, means-tested invoicing), installed and operated for you. Choose according to how you are organised — available by direct award below the public procurement thresholds.
Agility
Setup + controlled subscription
10,235 € incl. VAT setup
then 880 € 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,450 € 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,151 € incl. VAT setup
then 1,140 € 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 school department
Children's data never leaves the authorityLocal inference or an isolated resource hosted in France; no data entrusted to a foreign third party.
Data in France, under French lawFor children's data: hosting under French law, native minimisation, architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity.
The officer keeps the decisionThe AI agent prepares lists, notices and letters that can be checked; no placement is automated.
Human oversight & traceabilitySchool & out-of-school enrolment: every change to the service is logged, in line with the requirements of the AI Act.
Frequently asked questions
Your questions, our answers
Does the agent place the children?
No: it prepares; placements and exemptions remain decided by the officer and the elected member concerned.
Is children's data protected?
Yes: hosting in France, a resource isolated for each authority, a deployment governed with regard to the GDPR; no data outside the EU.
Does the agent handle catchment exemptions?
It assesses the request and prepares the decision, but granting an exemption remains an act of the department.
Does it integrate with our childcare/family software?
Yes: through secure integrations defined at the design stage (family portal, revenue office, school meals).
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 and handing over to your teams.
Do we need a technical team in-house?
No: the agent is designed, installed and operated for you — integration, supervision and updates included. Your teams concentrate on their work, with guided familiarisation.
Do we have to run a procurement procedure?
Below the public procurement thresholds, the agent is available by direct award. We supply what your decision needs: a quote, GDPR and AI Act documentation, and the hosting arrangements in France.
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 — are passed on at actual cost, with no margin, outside the subscription.
Let's talk
Let us estimate the potential in your authority
A few minutes to identify the most useful use case — hosted in France, supervised, with no commitment.