● Public sector — Cemeteries & burial plots
AI agent for managing cemeteries and burial plots
An assistant that prepares grant deeds, keeps the registers and answers families with tact — the officer checks and the authority decides. Hosted in France, on a resource isolated for each town: families' data stays protected. The AI agent assists, the public officer decides.
Hosted in France
Families' data protected
GDPR & AI Act: governed deployment
Human oversight
Updated on
Deployed in a few weeks
Cemeteries assistant · hosted in France
A family asks how to renew their parents' burial plot, which expires in September. Prepare a reply.
Reply drafted, with the tact required. It recalls the expiry of the thirty-year grant (plot B-12 in the register), the renewal arrangements set out in your regulations, the documents to provide and the rate adopted. The letter offers the department's help to the family.
Ready for review before sending.
⛓ Source · your cemetery regulations + the register of plots
Ready for review before sending.
⛓ Source · your cemetery regulations + the register of plots
Prepare the statement of plots expiring next quarter, with the draft letters to families.
Statement prepared. 14 plots are expiring: 11 with successors identified in the register, 3 with no known contact (a public notice procedure to consider). The reminder letters are drafted on your template, in a measured and considerate tone.
Each case refers back to its register entry for checking.
✎ Action · letters ready for review — the public officer approves and signs
Each case refers back to its register entry for checking.
✎ Action · letters ready for review — the public officer approves and signs
Local inference · no data outside the EU
Data hosted in France
Sovereign by designLocal inference or hosting in France
GDPR & AI Act: governed deploymentTraceability & human oversight
TurnkeyDesigned, installed and operated for you
The authority decidesThe agent assists, never approves alone
✦ In brief
In the cemeteries department, a Blue Lemon Agent agent prepares the grant deeds and renewals, supports the keeping of the registers and the tracking of expiry dates (renewals, reclaiming plots, statements), and drafts replies to families with the tact required. It runs on local inference or is hosted in France on a resource dedicated to and isolated for each town: 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. Every decision — allocation, reclaiming, renewal — remains an act of the department and the authority. 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 cemetery services — and why they hesitate
Managing cemeteries demands both legal rigour — grant deeds, registers, tightly regulated procedures for reclaiming plots — and great delicacy in dealing with families who are often bereaved. Old registers, scattered expiry dates and successors who are hard to trace all complicate the day-to-day.
! The issue
The department is caught between long, formal procedures — renewals, reclaiming plots, surveys — and families who deserve answers that are fair, quick and tactful. Yet most consumer AI tools amount to entrusting the identities of the deceased, families' contact details and the registers of plots to a third party, often hosted outside Europe and subject to the Cloud Act.
✓ Our answer
For data as sensitive as this, 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, decisions reserved to the department and the authority: every deed, every letter to a family is reviewed and signed by a public officer. The aim is not to replace the officer, but to give them back time for welcoming and supporting families.
The decisive point
Protecting families' data: sovereignty & compliance
Registers, deeds, successors' contact details: the cemeteries department handles particularly delicate personal data. Here is how the architecture of our agents protects it, town by town.
Local inference
The agent can run on a machine at the town: 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
As regards families' data, exposure to the Cloud Act and FISA 702 is reduced by design; location alone does not guarantee immunity.
One isolated resource per council
No pooling of data: an environment strictly dedicated to your town, 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
An agent strictly in support; no act signed automatically; traceability and human oversight from end to end.
What depends on the architecture chosen These points are not general guarantees: they are settled deployment by deployment, in the quotation.
- The applicable location is that of the architecture set out in the quotation and verified before commissioning.
- Local execution is announced only for the configuration explicitly described and accepted in the quotation.
- The applicable isolation depends on the deployment mode set out in the quotation; no dedicated isolation is presumed.
- The encryption mechanisms in transit and at rest, their components and key management are those documented for the architecture chosen.
- Roles and permissions are configured and accepted for the identities and systems actually connected.
- The events logged, their content, their retention period and who may access them are defined for the deployment chosen.
For the most sensitive data, SecNumCloud and HDS options are available depending on your requirements. A single architecture is designed to answer both the GDPR and extraterritorial exposure. Designed for deployment in line with the GDPR and the AI Act, after the processing, roles and context-specific risks have been assessed.
Demonstration
See the agent at work
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 bodyMunicipality of Bellemont-sur-Vère — population department, cemeteries and grants service (fictional authority)
- Sector
- Cemeteries service of a municipality of 12,600 inhabitants — 3 municipal cemeteries (Saint-Martin, opened in 1874; Le Clos-Fleuri; La Croix-Verte), a cremation site with columbarium and garden of remembrance, 4,780 plots of which 4,120 are grants in force
- Headcount
- 9 staff in the population department, 2 of them on cemeteries and grants — a grants officer and a deputy shared with civil registration; 4 groundstaff work on site and the AI assistant does not touch that
- Public served
- Grant holders and their successors in title — 2,940 enquiries a year: 1,640 calls, 780 emails, 420 desk visits, 100 website forms; 142 interments and urn placements a year
- Order of magnitude
- 4,120 grants in force — 1,486 in perpetuity, 1,940 thirty-year, 694 fifteen-year — and 268 columbarium niches; 58 expiries a year, 14 of them in the coming quarter; 96 deeds prepared each year (38 new grants, 44 renewals, 14 miscellaneous deeds); 24 reclamation files in progress
- Tools already in place
- Cemetery management software (register, map, plots), bound registers from 1874 to 1978 digitised as unindexed images, revenue office, the service's own deed and letter templates, department mailbox and Microsoft Teams — the assistant connects read-only, no software is replaced or migrated
- Who decides what
- The mayor signs grant deeds and orders; the head of the population department validates every letter to a family before it goes out; grant tariffs are set by resolution of the town council; a reclamation is decided by the town council and then pronounced by order of the mayor
- Room for improvement
- 11 of the 58 expiries in the past year were noticed after the date; 118 grants have no contactable successor in the register; finding a plot in the bound registers predating 1978 takes 38 minutes on average; an email from a family waits 6 days; and 4 of the 24 reclamation files in progress carry no record of notification to the successors in title
In Bellemont-sur-Vère, two officers hold 4,120 grants across three cemeteries, the oldest of which opened in 1874. The computerised register goes back to 1978; before that date, entries live in bound registers digitised as images that nothing indexes. Expiries, renewal requests and reclamation files are tracked by hand, and every exchange is with families many of whom have just lost someone. The exchanges below cover one year, from the reconciliation of the register to the review presented to the town council. The assistant is hosted in France on an isolated resource, reads the management software and the registers without ever writing to them, and no deed, no letter and no reclamation goes out without the signature or validation of a named person.
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.
Cemeteries assistant · hosted in France
I have reread your 2,940 enquiries for the year and reconciled, plot by plot, your computerised register, the cemetery maps and the signed deeds — the reconciliation day-to-day work never leaves time for.
What the count says: 10 topics cover 2,240 enquiries out of 2,940, i.e. 76.1%. Locating a grave, opening hours and access to the three cemeteries, formalities after a death, documents for a grant application, terms and renewal, columbarium and garden of remembrance, works and memorial stones, placing and removing an urn, upkeep and flowers, searching the old registers. The 10 reference answers are written on your cemetery by-law and on the resolution of 18 November 2025, dated, and drafted in the restrained tone you have set — they are waiting for you.
What the three items you can check against your own files are worth:
· Preparing a grant deed takes 48 minutes, 60% of it on searching the register, carrying over the particulars and checking terms and tariffs — 28 minutes 48.
· An expiry reminder letter takes 32 minutes, 40% of it on the drafting itself — 12 minutes 48.
· The quarterly statement of expiries and reclamations is 100% manual work: 3 working days for your two officers, i.e. 42 hours per quarter.
And the gap the reconciliation found, in Saint-Martin cemetery alone — 1,480 plots: 47 discrepancies, never seen because nobody ever had the three days to look. 26 plots shown on the map and absent from the computerised register, all from the bound registers predating 1978; 11 expiries passed with no record and no letter on file; 7 signed deeds whose term in the register differs from the term in the deed; 3 plots entered twice under two numbers.
These 47 discrepancies are not lines in a file. They are 47 situations in which a family could receive a letter the register does not support — and, among the 11 expiries passed, 4 are still within the two-year period that article L. 2223-15 of the French general local authorities code allows the grant holder and their successors to request renewal. Those four families can still be told in good time.
The next step, and it takes an hour: you reread the 47 lines and tell me, for each, what you want done. The head of department signs off the version, and the 4 letters that matter go out this week. cemeteries-service-flow_2940-enquiries-10-topics.pdf2,240 enquiries across 10 topics, the three items costed, 863 hours identified
⛓ Sourced · 12 months of enquiry logs, computerised register, maps of the three cemeteries, signed deeds, resolution of 18 November 2025
What the count says: 10 topics cover 2,240 enquiries out of 2,940, i.e. 76.1%. Locating a grave, opening hours and access to the three cemeteries, formalities after a death, documents for a grant application, terms and renewal, columbarium and garden of remembrance, works and memorial stones, placing and removing an urn, upkeep and flowers, searching the old registers. The 10 reference answers are written on your cemetery by-law and on the resolution of 18 November 2025, dated, and drafted in the restrained tone you have set — they are waiting for you.
What the three items you can check against your own files are worth:
· Preparing a grant deed takes 48 minutes, 60% of it on searching the register, carrying over the particulars and checking terms and tariffs — 28 minutes 48.
· An expiry reminder letter takes 32 minutes, 40% of it on the drafting itself — 12 minutes 48.
· The quarterly statement of expiries and reclamations is 100% manual work: 3 working days for your two officers, i.e. 42 hours per quarter.
And the gap the reconciliation found, in Saint-Martin cemetery alone — 1,480 plots: 47 discrepancies, never seen because nobody ever had the three days to look. 26 plots shown on the map and absent from the computerised register, all from the bound registers predating 1978; 11 expiries passed with no record and no letter on file; 7 signed deeds whose term in the register differs from the term in the deed; 3 plots entered twice under two numbers.
These 47 discrepancies are not lines in a file. They are 47 situations in which a family could receive a letter the register does not support — and, among the 11 expiries passed, 4 are still within the two-year period that article L. 2223-15 of the French general local authorities code allows the grant holder and their successors to request renewal. Those four families can still be told in good time.
The next step, and it takes an hour: you reread the 47 lines and tell me, for each, what you want done. The head of department signs off the version, and the 4 letters that matter go out this week. cemeteries-service-flow_2940-enquiries-10-topics.pdf2,240 enquiries across 10 topics, the three items costed, 863 hours identified
⛓ Sourced · 12 months of enquiry logs, computerised register, maps of the three cemeteries, signed deeds, resolution of 18 November 2025
47 discrepancies in one cemetery. What does that give across all three, and how do we avoid accumulating new ones?
Across your 4,780 plots, the same reconciliation rule finds 152. That is not a cost figure: it is a risk figure. Every discrepancy is an opportunity to write to the wrong person, to let an expiry pass that a family would have wanted to honour, or to begin a procedure on a date the file does not prove. In this work, a mistake cannot always be undone.
What I have done on top, and what day-to-day work never leaves time for: I have written four control rules, in the language of your cemetery by-law, and run them across the 4,780 plots and the last 24 months of files. For each one I give you the alerts produced, the share confirmed on examination, and what it lets through:
· Rule A — a plot shown on the map with no record in the computerised register: 84 alerts, 84 confirmed — 100%. All come from the bound registers predating 1978.
· Rule B — a grant term in the register differing from the term in the signed deed: 23 alerts, 21 confirmed — 91.3%. The other 2 are lawful conversions whose supplementary deed exists but was not attached to the record.
· Rule C — an expiry passed with no record and no letter on file: 36 alerts, 36 confirmed — 100%.
And here is what those three rules let through, because you need to know before you sign: 12 plots are entered twice, under two numbers, and none of the three sees them. So I wrote rule D — two records designating the same plot or the same deceased person under two numbers — and ran it over the same scope: 12 alerts, 11 confirmed.
The four rules together: 155 alerts, 152 confirmed, covering 152 of the 164 discrepancies found across the scope — 92.6%.
Bringing a rule into service stays with the department: a rule only takes effect once the head of department has approved it. I save you the writing and the measurement; the decision takes an hour instead of a committee.
And I write nothing to the register: I produce a correction file, line by line, each line carrying the document that supports it — the deed, the map, the page of the bound register. Your grants officer imports line by line, and a correction refused stays refused. register-discrepancies_4-rules-tested-across-4780-plots.pdfThe 47 Saint-Martin discrepancies in detail, 4 rules tested, 152 discrepancies out of 164 covered
⛓ Sourced · 4,780 plots, maps of the three cemeteries, signed deeds, bound registers 1874-1978, 24 months of files
What I have done on top, and what day-to-day work never leaves time for: I have written four control rules, in the language of your cemetery by-law, and run them across the 4,780 plots and the last 24 months of files. For each one I give you the alerts produced, the share confirmed on examination, and what it lets through:
· Rule A — a plot shown on the map with no record in the computerised register: 84 alerts, 84 confirmed — 100%. All come from the bound registers predating 1978.
· Rule B — a grant term in the register differing from the term in the signed deed: 23 alerts, 21 confirmed — 91.3%. The other 2 are lawful conversions whose supplementary deed exists but was not attached to the record.
· Rule C — an expiry passed with no record and no letter on file: 36 alerts, 36 confirmed — 100%.
And here is what those three rules let through, because you need to know before you sign: 12 plots are entered twice, under two numbers, and none of the three sees them. So I wrote rule D — two records designating the same plot or the same deceased person under two numbers — and ran it over the same scope: 12 alerts, 11 confirmed.
The four rules together: 155 alerts, 152 confirmed, covering 152 of the 164 discrepancies found across the scope — 92.6%.
Bringing a rule into service stays with the department: a rule only takes effect once the head of department has approved it. I save you the writing and the measurement; the decision takes an hour instead of a committee.
And I write nothing to the register: I produce a correction file, line by line, each line carrying the document that supports it — the deed, the map, the page of the bound register. Your grants officer imports line by line, and a correction refused stays refused. register-discrepancies_4-rules-tested-across-4780-plots.pdfThe 47 Saint-Martin discrepancies in detail, 4 rules tested, 152 discrepancies out of 164 covered
⛓ Sourced · 4,780 plots, maps of the three cemeteries, signed deeds, bound registers 1874-1978, 24 months of files
Our registers carry the names of the deceased, dates, and the contact details of their families. Where does that data 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 Bellemont-sur-Vère and to nobody else — or on a machine belonging to the municipality if you prefer local inference, in which case nothing even leaves the network. No 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.
One distinction is useful here, and it is little known: the General Data Protection Regulation does not apply to the data of deceased persons — its recital 27 says so expressly. It applies in full to the living whose contact details your register carries: grant holders, successors in title, agents. That is where the requirement lies, and that is where I hold it. French law adds, in the Data Protection Act, the possibility for anyone to leave directions on what becomes of their data after their death: if such directions are given to you, I flag them on the record concerned rather than leaving them to sit in a letter.
What I read, and what I cannot reach: I have read-only access to the register, the maps, the deeds and the digitised bound registers. I have no write access to the cemetery management software: I produce files and drafts, your officer imports them. Bank details and revenue office documents are not open to me — I have no use for them in preparing a deed, 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.
What you can show your data protection officer: every read is logged with its date, its purpose and the record concerned; every output carries the documents it is drawn from; and the record of processing activities is already written — public interest task for funeral policing and the management of grants, 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 families' data lives, who reads what, what is withdrawn on a word
✎ Framework · hosting architecture, access log, population department record of processing activities
Where I run: on an isolated resource hosted in France, under French law, dedicated to Bellemont-sur-Vère and to nobody else — or on a machine belonging to the municipality if you prefer local inference, in which case nothing even leaves the network. No 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.
One distinction is useful here, and it is little known: the General Data Protection Regulation does not apply to the data of deceased persons — its recital 27 says so expressly. It applies in full to the living whose contact details your register carries: grant holders, successors in title, agents. That is where the requirement lies, and that is where I hold it. French law adds, in the Data Protection Act, the possibility for anyone to leave directions on what becomes of their data after their death: if such directions are given to you, I flag them on the record concerned rather than leaving them to sit in a letter.
What I read, and what I cannot reach: I have read-only access to the register, the maps, the deeds and the digitised bound registers. I have no write access to the cemetery management software: I produce files and drafts, your officer imports them. Bank details and revenue office documents are not open to me — I have no use for them in preparing a deed, 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.
What you can show your data protection officer: every read is logged with its date, its purpose and the record concerned; every output carries the documents it is drawn from; and the record of processing activities is already written — public interest task for funeral policing and the management of grants, 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 families' data lives, who reads what, what is withdrawn on a word
✎ Framework · hosting architecture, access log, population department record of processing activities
A family is asking how to renew their parents' grant, which expires in September. Draft a reply.
Reply drafted, with the tact required. It sets out the expiry of the thirty-year grant — plot B-12 in the register, Saint-Martin cemetery, deed of 14 September 1996 —, the renewal arrangements provided for by your cemetery by-law, the documents to be supplied and the tariff as resolved, taken without rewording from the schedule adopted on 18 November 2025. The letter expresses the service's readiness to assist the family. Ready for reading before sending.
What the letter says and families often do not know: article L. 2223-15 of the French general local authorities code allows the grant holder and their successors two years after expiry to request renewal. That sentence is written to reassure, not to warn: a family receiving an expiry reminder often fears it has already lost everything, and it is fairer to say at once that there is time.
The renewal deed is prepared at the same time, on your template: identity of the grant holder, plot, nature and term, mandatory particulars carried over from the original deed, applicable tariff. The documents the family attached have been checked: family record book and death certificate present, standing as successor established by descent. One item is missing: the written agreement of the second daughter, named in the 1996 deed — and the letter asks for it considerately, explaining why it is required rather than simply demanding it.
What that is worth over the year: your 96 deeds go from 28 minutes 48 of preparation to 4 minutes 48 — 60% of the deed's time down to 10%, i.e. 38 hours returned to the service. And your letters to families go from 12 minutes 48 of drafting to 3 minutes 12 — 40% down to 10%, i.e. 102 hours across 640 letters.
Nothing is signed: a grant deed is an act of the mayor. I prepare it complete and verifiable; the signature stays where it belongs, and it is the signature that makes the deed good against anyone who might dispute it. grant-deed_renewal-plot-b-12.pdfThe letter to the family, the renewal deed prepared, the documents checked
⛓ Sourced · register of grants (plot B-12), deed of 14 September 1996, cemetery by-law, tariff resolution of 18 November 2025
What the letter says and families often do not know: article L. 2223-15 of the French general local authorities code allows the grant holder and their successors two years after expiry to request renewal. That sentence is written to reassure, not to warn: a family receiving an expiry reminder often fears it has already lost everything, and it is fairer to say at once that there is time.
The renewal deed is prepared at the same time, on your template: identity of the grant holder, plot, nature and term, mandatory particulars carried over from the original deed, applicable tariff. The documents the family attached have been checked: family record book and death certificate present, standing as successor established by descent. One item is missing: the written agreement of the second daughter, named in the 1996 deed — and the letter asks for it considerately, explaining why it is required rather than simply demanding it.
What that is worth over the year: your 96 deeds go from 28 minutes 48 of preparation to 4 minutes 48 — 60% of the deed's time down to 10%, i.e. 38 hours returned to the service. And your letters to families go from 12 minutes 48 of drafting to 3 minutes 12 — 40% down to 10%, i.e. 102 hours across 640 letters.
Nothing is signed: a grant deed is an act of the mayor. I prepare it complete and verifiable; the signature stays where it belongs, and it is the signature that makes the deed good against anyone who might dispute it. grant-deed_renewal-plot-b-12.pdfThe letter to the family, the renewal deed prepared, the documents checked
⛓ Sourced · register of grants (plot B-12), deed of 14 September 1996, cemetery by-law, tariff resolution of 18 November 2025
Families call us, often in the days after a death. We cannot put an answering machine in front of them, and we cannot put a machine in front of them either.
You are right, and that is the rule I hold: I take the formalities, I never take the conversation.
What I handle end to end: the 10 topics whose answers are approved and dated — opening hours and access, locating a grave, documents for an application, terms and renewal, columbarium and garden of remembrance, works, urn placement, upkeep, old registers, formalities after a death. These are questions of documents and procedure, and a family that gets its answer at ten in the evening on a Sunday does not have to call back on Monday.
What I do not handle end to end, and this is a service rule, not a technical limit: as soon as a message touches on a personal situation — a disagreement between heirs, a request for exhumation, a recent bereavement expressed —, it is passed to an officer of the service, with the file assembled and the message in full. Your officer picks the conversation up where it stands, without making the family repeat itself. That is what you have set, and it does not drift on its own.
What I state, and I always state it: I am an artificial intelligence, and I say so in my first sentence — article 50(1) of the European AI regulation has required this since 2 August 2026 — and anyone may ask for an officer of the service at any time, without having to justify it. Over the year, 312 families asked, and all 312 were given an officer.
On which channels: WhatsApp Business, the site chat and email, with no account to create and no app to install — what matters here is older people and families living far away, for whom an online form is a real obstacle. Your own staff consult me from Microsoft Teams, Slack or their mailbox, without changing tools. Email, which waits 6 days today, goes back to 1 day.
The figure that does not flatter me, and I publish it: across the 612 grave-location enquiries of the first quarter, I gave the wrong plot in 14 cases — 2.3%. All fourteen concerned surnames present in two cemeteries, and I was answering on the more recent record. That is fixed, and the fix is a rule of conduct as much as a setting: when two records carry the same name, I do not choose — I present both, with their cemetery and their date, and the family recognises its own. In the second quarter, 1 case out of 612 — 0.2%. I will go on publishing that rate every quarter. family-channels_restrained-tone-and-transfer-to-an-officer.pdfThe 10 topics handled end to end, the grounds for immediate transfer, the published error rate
⛓ Sourced · 12 months of exchange logs, log of transfers to an officer, cemetery by-law, register of the three cemeteries
What I handle end to end: the 10 topics whose answers are approved and dated — opening hours and access, locating a grave, documents for an application, terms and renewal, columbarium and garden of remembrance, works, urn placement, upkeep, old registers, formalities after a death. These are questions of documents and procedure, and a family that gets its answer at ten in the evening on a Sunday does not have to call back on Monday.
What I do not handle end to end, and this is a service rule, not a technical limit: as soon as a message touches on a personal situation — a disagreement between heirs, a request for exhumation, a recent bereavement expressed —, it is passed to an officer of the service, with the file assembled and the message in full. Your officer picks the conversation up where it stands, without making the family repeat itself. That is what you have set, and it does not drift on its own.
What I state, and I always state it: I am an artificial intelligence, and I say so in my first sentence — article 50(1) of the European AI regulation has required this since 2 August 2026 — and anyone may ask for an officer of the service at any time, without having to justify it. Over the year, 312 families asked, and all 312 were given an officer.
On which channels: WhatsApp Business, the site chat and email, with no account to create and no app to install — what matters here is older people and families living far away, for whom an online form is a real obstacle. Your own staff consult me from Microsoft Teams, Slack or their mailbox, without changing tools. Email, which waits 6 days today, goes back to 1 day.
The figure that does not flatter me, and I publish it: across the 612 grave-location enquiries of the first quarter, I gave the wrong plot in 14 cases — 2.3%. All fourteen concerned surnames present in two cemeteries, and I was answering on the more recent record. That is fixed, and the fix is a rule of conduct as much as a setting: when two records carry the same name, I do not choose — I present both, with their cemetery and their date, and the family recognises its own. In the second quarter, 1 case out of 612 — 0.2%. I will go on publishing that rate every quarter. family-channels_restrained-tone-and-transfer-to-an-officer.pdfThe 10 topics handled end to end, the grounds for immediate transfer, the published error rate
⛓ Sourced · 12 months of exchange logs, log of transfers to an officer, cemetery by-law, register of the three cemeteries
We are often asked to find an old grave. In the bound registers that can take an hour, and sometimes we do not find it.
The 1,240 records held in the bound registers from 1874 to 1978 are now legible and searchable — and that is the work nobody had time to undertake.
What I have done: I have read the digitised images of your registers and extracted, page by page, the surname, given names, date of interment, plot number and map reference. Each record carries a link to the image of the page it is drawn from, so that your officer verifies the source in one click rather than taking my word for it.
What the reading gives, honestly: 1,240 records extracted, of which 1,118 have all five fields complete — 90.2%. For the other 122, at least one entry is illegible or uncertain, and I present them as such: the record reads « to be confirmed against the original » rather than a value I cannot guarantee. An uncertain record declared uncertain is usable; an uncertain record presented as certain is not.
What that changes at the desk: a search for an old plot goes from 38 minutes to 2 minutes — 252 hours returned across the year's 420 searches — and above all a family that has travelled a long way leaves with the path, the row and the number the same day, instead of « we will call you back ».
What I disclose and what I do not: the plot, the date of interment and the names of those interred are given. The contact details of living successors in title are never given to a third party — they are data about living people, and a genealogical purpose does not open them. When a third party is trying to reach a family, I prepare a letter the service can forward: that is the path that achieves the same result without exposing anyone.
The next step I suggest: going back over the 122 uncertain records in batches of twenty, during visits to Saint-Martin cemetery — the stone often carries what the register has lost, and comparing the two closes most cases. register-discrepancies_4-rules-tested-across-4780-plots.pdfIndexing of the 1,240 old records, the 122 records flagged uncertain
⛓ Sourced · bound registers 1874-1978 digitised, map of Saint-Martin cemetery, computerised register
What I have done: I have read the digitised images of your registers and extracted, page by page, the surname, given names, date of interment, plot number and map reference. Each record carries a link to the image of the page it is drawn from, so that your officer verifies the source in one click rather than taking my word for it.
What the reading gives, honestly: 1,240 records extracted, of which 1,118 have all five fields complete — 90.2%. For the other 122, at least one entry is illegible or uncertain, and I present them as such: the record reads « to be confirmed against the original » rather than a value I cannot guarantee. An uncertain record declared uncertain is usable; an uncertain record presented as certain is not.
What that changes at the desk: a search for an old plot goes from 38 minutes to 2 minutes — 252 hours returned across the year's 420 searches — and above all a family that has travelled a long way leaves with the path, the row and the number the same day, instead of « we will call you back ».
What I disclose and what I do not: the plot, the date of interment and the names of those interred are given. The contact details of living successors in title are never given to a third party — they are data about living people, and a genealogical purpose does not open them. When a third party is trying to reach a family, I prepare a letter the service can forward: that is the path that achieves the same result without exposing anyone.
The next step I suggest: going back over the 122 uncertain records in batches of twenty, during visits to Saint-Martin cemetery — the stone often carries what the register has lost, and comparing the two closes most cases. register-discrepancies_4-rules-tested-across-4780-plots.pdfIndexing of the 1,240 old records, the 122 records flagged uncertain
⛓ Sourced · bound registers 1874-1978 digitised, map of Saint-Martin cemetery, computerised register
Prepare the statement of grants expiring next quarter, with the draft letters to families.
Statement prepared. 14 grants are due to expire: 11 with successors in title identified in the register, 3 with no known contact — public notice procedure to be considered. The reminder letters are drafted on your template, in a measured and considerate tone. Each case refers back to its register record for checking.
The 11 files with a contact, in detail: for each, the date of the deed, the term, the expiry date, the last known successor and the date they were last reached. Three of those addresses are more than ten years old: I flag them, because a letter that comes back is a month lost on a time limit that is running. For those three I suggest a letter backed by a phone call, and the number is on the file.
The 3 files with no known contact: I do not present them as lost. For each I have gone back over the original deed, its particulars, the successive interments and the bound registers — and two of them carry a successor's name that still appears in another of your cemetery files, with an address less than three years old. Both letters are ready. The third does indeed call for the public notice your by-law provides for, and the draft notice is written, with the plot, the display period and the date of removal.
What each letter tells the family, and it matters: the two-year period after expiry that article L. 2223-15 of the general local authorities code allows for requesting renewal. Telling people early and stating the time limit is how you prevent someone finding out when it is too late.
What that is worth: 42 hours per quarter today, 3 working days for two officers. Afterwards: 8 hours 24 of checking and validation, i.e. 20% of the current time. 33 hours returned per quarter, 134 hours over the year.
The next step I suggest: moving the statement from three months ahead to twelve. Over the past year, 11 of your 58 expiries were noticed after the date; twelve months ahead, none of those eleven would have escaped the first letter. statement-of-expiries_14-grants-this-quarter.pdfThe 14 expiries file by file, the 11 letters ready, the draft public notice
✎ Action · statement prepared — the head of department validates, the mayor signs · register of grants, cemetery by-law, article L. 2223-15 of the general local authorities code
The 11 files with a contact, in detail: for each, the date of the deed, the term, the expiry date, the last known successor and the date they were last reached. Three of those addresses are more than ten years old: I flag them, because a letter that comes back is a month lost on a time limit that is running. For those three I suggest a letter backed by a phone call, and the number is on the file.
The 3 files with no known contact: I do not present them as lost. For each I have gone back over the original deed, its particulars, the successive interments and the bound registers — and two of them carry a successor's name that still appears in another of your cemetery files, with an address less than three years old. Both letters are ready. The third does indeed call for the public notice your by-law provides for, and the draft notice is written, with the plot, the display period and the date of removal.
What each letter tells the family, and it matters: the two-year period after expiry that article L. 2223-15 of the general local authorities code allows for requesting renewal. Telling people early and stating the time limit is how you prevent someone finding out when it is too late.
What that is worth: 42 hours per quarter today, 3 working days for two officers. Afterwards: 8 hours 24 of checking and validation, i.e. 20% of the current time. 33 hours returned per quarter, 134 hours over the year.
The next step I suggest: moving the statement from three months ahead to twelve. Over the past year, 11 of your 58 expiries were noticed after the date; twelve months ahead, none of those eleven would have escaped the first letter. statement-of-expiries_14-grants-this-quarter.pdfThe 14 expiries file by file, the 11 letters ready, the draft public notice
✎ Action · statement prepared — the head of department validates, the mayor signs · register of grants, cemetery by-law, article L. 2223-15 of the general local authorities code
And reclamations? That is the part that worries us most, because a mistake there cannot be undone.
It cannot, and that is precisely why a reclamation must rest only on dates the file proves. Your 24 files in progress are sorted by stage, each with the complete chain of dates and documents.
The two regimes are not alike, and I keep them apart:
· Grant expired and not renewed. Article L. 2223-15 of the general local authorities code opens a two-year period after expiry during which renewal remains possible. I keep that countdown file by file, and I give you the exact date on which it closes.
· Perpetual grant in a state of abandonment. Articles L. 2223-17 and L. 2223-18 of the same code frame a long procedure: it may be begun only thirty years after the grant deed and ten years after the last interment, it requires a record of abandonment notified to the successors in title and publicly displayed, then a second record three years after the first, before the town council's resolution and the mayor's order. Each of those dates is on the file, with the document that establishes it.
Where your 24 files stand:
· 5 do not yet meet the age conditions — for each I give the date on which it will, and there is nothing to do until then;
· 9 meet them and await a first record of abandonment — the 9 drafts are written on your template, with the condition observed, the date and the particulars;
· 6 carry a first record more than three years old — the second can be drawn up, and the 6 drafts are written;
· 4 carry a first record but no trace of notification to the successors in title and no public display. Those four I take out of the queue. This is not a delay I am imposing on you: it is what the service would have lost. A reclamation whose notification is not proved is a reclamation a family can overturn, and they would then learn of it through litigation rather than through a letter. For all four I have prepared the renewed notification and public display, with the calendar that follows.
On what becomes of the remains, because the question always comes and deserves an exact answer: article L. 2223-4 of the general local authorities code requires the municipality to have an ossuary, where exhumed remains are placed, and to keep a record of the names of those who rest there. I keep that record up to date, name by name and date by date — because it is the record a family will come to consult in twenty years, and there is no way to reconstruct it afterwards.
Nothing is begun without you: no procedure is opened, no record of abandonment is drawn up, no order is made. I keep the dates, I write the drafts, I flag what is missing; the decision belongs to the town council and the mayor. reclamation-procedure_24-files-and-their-time-limits.pdfThe 24 files by stage, the dates to be proved, the 4 files taken out of the queue
✎ Framework · 24 reclamation files, register of grants, ossuary record, articles L. 2223-4, L. 2223-15, L. 2223-17 and L. 2223-18 of the general local authorities code
The two regimes are not alike, and I keep them apart:
· Grant expired and not renewed. Article L. 2223-15 of the general local authorities code opens a two-year period after expiry during which renewal remains possible. I keep that countdown file by file, and I give you the exact date on which it closes.
· Perpetual grant in a state of abandonment. Articles L. 2223-17 and L. 2223-18 of the same code frame a long procedure: it may be begun only thirty years after the grant deed and ten years after the last interment, it requires a record of abandonment notified to the successors in title and publicly displayed, then a second record three years after the first, before the town council's resolution and the mayor's order. Each of those dates is on the file, with the document that establishes it.
Where your 24 files stand:
· 5 do not yet meet the age conditions — for each I give the date on which it will, and there is nothing to do until then;
· 9 meet them and await a first record of abandonment — the 9 drafts are written on your template, with the condition observed, the date and the particulars;
· 6 carry a first record more than three years old — the second can be drawn up, and the 6 drafts are written;
· 4 carry a first record but no trace of notification to the successors in title and no public display. Those four I take out of the queue. This is not a delay I am imposing on you: it is what the service would have lost. A reclamation whose notification is not proved is a reclamation a family can overturn, and they would then learn of it through litigation rather than through a letter. For all four I have prepared the renewed notification and public display, with the calendar that follows.
On what becomes of the remains, because the question always comes and deserves an exact answer: article L. 2223-4 of the general local authorities code requires the municipality to have an ossuary, where exhumed remains are placed, and to keep a record of the names of those who rest there. I keep that record up to date, name by name and date by date — because it is the record a family will come to consult in twenty years, and there is no way to reconstruct it afterwards.
Nothing is begun without you: no procedure is opened, no record of abandonment is drawn up, no order is made. I keep the dates, I write the drafts, I flag what is missing; the decision belongs to the town council and the mayor. reclamation-procedure_24-files-and-their-time-limits.pdfThe 24 files by stage, the dates to be proved, the 4 files taken out of the queue
✎ Framework · 24 reclamation files, register of grants, ossuary record, articles L. 2223-4, L. 2223-15, L. 2223-17 and L. 2223-18 of the general local authorities code
How do we bring your four rules into service? And what if one of them starts flagging wrongly?
One at a time, each with its entry figure, and none starts without your approval.
The order I recommend, and the arithmetic behind it: rule C first — 36 alerts, 100% confirmed, and it is the only one where every line concerns a family that must be told; then A — 84 alerts, 100% confirmed, but it is register work, urgent for nobody; then B, then D. I advise against switching them on in the same month, and I cost it: the four together would produce 155 alerts to examine, i.e. around 26 hours for your two officers. One per quarter is between 2 and 14 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, quarter after quarter. A rule that drops below 80% confirmation makes you examine files for nothing: I warn you in the very quarter concerned, with the tightened version already written and already run across the scope, as I did for rule B — its first drafting flagged every difference of term between register and deed and produced 61 alerts for 21 confirmed (34.4%), because it counted the lawful conversions whose supplementary deed exists; the tightened version, which attaches the supplementary deeds first, produces 23 for 21 confirmed — the 21 genuine ones kept, 38 files spared being opened 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 the municipality: signing a deed, sending a letter to a family, opening a reclamation procedure, correcting a register record are acts of the department and of the authority. 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 item-by-item reading) to the broadest (acknowledgements and expiry reminders go out on their own, anything touching a reclamation waits). On this work I recommend the intermediate scope, and I say so even though it is the narrowest: a reclamation letter sent too quickly cannot be undone.
And withdrawal is as simple as going live: a rule stops on a word, within the second, and the records it had held return to the normal flow, with the reason and the date of the withdrawal. register-discrepancies_4-rules-tested-across-4780-plots.pdfThe go-live schedule, the tightened version of rule B, the three-setting mandate
⛓ Sourced · comparative measurement of the two draftings of rule B, 4,780 plots, cemetery by-law
The order I recommend, and the arithmetic behind it: rule C first — 36 alerts, 100% confirmed, and it is the only one where every line concerns a family that must be told; then A — 84 alerts, 100% confirmed, but it is register work, urgent for nobody; then B, then D. I advise against switching them on in the same month, and I cost it: the four together would produce 155 alerts to examine, i.e. around 26 hours for your two officers. One per quarter is between 2 and 14 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, quarter after quarter. A rule that drops below 80% confirmation makes you examine files for nothing: I warn you in the very quarter concerned, with the tightened version already written and already run across the scope, as I did for rule B — its first drafting flagged every difference of term between register and deed and produced 61 alerts for 21 confirmed (34.4%), because it counted the lawful conversions whose supplementary deed exists; the tightened version, which attaches the supplementary deeds first, produces 23 for 21 confirmed — the 21 genuine ones kept, 38 files spared being opened 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 the municipality: signing a deed, sending a letter to a family, opening a reclamation procedure, correcting a register record are acts of the department and of the authority. 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 item-by-item reading) to the broadest (acknowledgements and expiry reminders go out on their own, anything touching a reclamation waits). On this work I recommend the intermediate scope, and I say so even though it is the narrowest: a reclamation letter sent too quickly cannot be undone.
And withdrawal is as simple as going live: a rule stops on a word, within the second, and the records it had held return to the normal flow, with the reason and the date of the withdrawal. register-discrepancies_4-rules-tested-across-4780-plots.pdfThe go-live schedule, the tightened version of rule B, the three-setting mandate
⛓ Sourced · comparative measurement of the two draftings of rule B, 4,780 plots, cemetery by-law
The town council is asking for a twelve-month review. What do we present?
Four figures, and each one can be checked against your own files.
· 863 hours returned to the service over the year, item by item: 38 h on preparing deeds, 102 h on letters to families, 134 h on the four quarterly statements, 336 h on routine enquiries, 252 h on searches for old plots. On the statutory working week of 35 hours, that is more than twenty-four weeks — more than five months — returned to your two officers. No post cut, no post created: it is time returned to the desk and to supporting families, which is the part of the work no tool replaces.
· Email goes from 6 days to 1 day, and a search for an old plot from 38 minutes to 2. The 1,240 records in the bound registers from 1874 to 1978 are searchable, 122 of them flagged as to be confirmed against the original.
· 152 discrepancies found between register, maps and deeds, and corrected line by line after checking. These are not savings: they are 152 letters that will not go to the wrong person.
· 0 deeds signed without the mayor, 0 reclamations begun without a resolution, 0 letters sent without validation, 0 items of data outside the European Union.
What I bring you on top: the state of the municipality's funerary estate, current and dated — plots occupied and free by cemetery, grants by term, expiries over the coming twelve months, reclamation files by stage, columbarium occupancy. Every figure carries the query that produces it, so that a councillor who asks where it comes from gets the answer in the meeting. The review is still written and presented by the department: it is an act of the municipality.
The next step I suggest for the coming year: your 268 columbarium niches are 91% occupied, and 4 of the 14 expiries this quarter concern grants of less than two square metres. I suggest measuring, over twelve months, the share of requests going to the cremation site rather than to an earth grave. It is a protocol, not a forecast: if the balance does not move, you will hear it from me. year-review_863-hours-item-by-item.pdfThe 863 hours in detail, the turnaround times held, the state of the funerary estate
⛓ Sourced · 12 months of department logs, register of grants, maps of the three cemeteries, reclamation files
· 863 hours returned to the service over the year, item by item: 38 h on preparing deeds, 102 h on letters to families, 134 h on the four quarterly statements, 336 h on routine enquiries, 252 h on searches for old plots. On the statutory working week of 35 hours, that is more than twenty-four weeks — more than five months — returned to your two officers. No post cut, no post created: it is time returned to the desk and to supporting families, which is the part of the work no tool replaces.
· Email goes from 6 days to 1 day, and a search for an old plot from 38 minutes to 2. The 1,240 records in the bound registers from 1874 to 1978 are searchable, 122 of them flagged as to be confirmed against the original.
· 152 discrepancies found between register, maps and deeds, and corrected line by line after checking. These are not savings: they are 152 letters that will not go to the wrong person.
· 0 deeds signed without the mayor, 0 reclamations begun without a resolution, 0 letters sent without validation, 0 items of data outside the European Union.
What I bring you on top: the state of the municipality's funerary estate, current and dated — plots occupied and free by cemetery, grants by term, expiries over the coming twelve months, reclamation files by stage, columbarium occupancy. Every figure carries the query that produces it, so that a councillor who asks where it comes from gets the answer in the meeting. The review is still written and presented by the department: it is an act of the municipality.
The next step I suggest for the coming year: your 268 columbarium niches are 91% occupied, and 4 of the 14 expiries this quarter concern grants of less than two square metres. I suggest measuring, over twelve months, the share of requests going to the cremation site rather than to an earth grave. It is a protocol, not a forecast: if the balance does not move, you will hear it from me. year-review_863-hours-item-by-item.pdfThe 863 hours in detail, the turnaround times held, the state of the funerary estate
⛓ Sourced · 12 months of department logs, register of grants, maps of the three cemeteries, reclamation files
In practical terms, what does the assistant do without asking us? That is the question the council will put.
Three actions, not one more, and all three can be undone.
· I acknowledge every family enquiry within the minute, giving the name of the officer who will handle the file and the response time. And the reverse is true as well: if an officer of the service has already replied, no automatic acknowledgement goes out on top of their reply — receiving a machine message after a human reply undoes the care that has just been taken.
· I flag every expiry twelve months ahead, then six months ahead, then on the date. And the reverse is true as well: as soon as a renewal is recorded, the remaining reminders stop within the second. A family that has done what was needed does not receive a reminder.
· I hold for checking any register record that triggers a rule in service. And the reverse is true as well: the grants officer clears it on a word, the record returns to the normal flow, with the reason and the date of the clearance — which gives you, the following quarter, the most frequent reasons, and therefore the rules to tighten.
Everything else waits for a named decision: no deed is signed, no plot is allocated, no register record is amended, no reclamation procedure is opened, no record of abandonment is drawn up, no letter goes out.
A word on a measurement I can produce and would advise you not to install as it stands: the number of files handled per 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 get pushed back in favour of the short ones. Here, the long files are a disagreement between heirs, an old reclamation, an illegible bound register — that is, exactly the situations where a family most needs someone to take time with them. 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 a letter and whoever signs a deed 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 family enquiry within the minute, giving the name of the officer who will handle the file and the response time. And the reverse is true as well: if an officer of the service has already replied, no automatic acknowledgement goes out on top of their reply — receiving a machine message after a human reply undoes the care that has just been taken.
· I flag every expiry twelve months ahead, then six months ahead, then on the date. And the reverse is true as well: as soon as a renewal is recorded, the remaining reminders stop within the second. A family that has done what was needed does not receive a reminder.
· I hold for checking any register record that triggers a rule in service. And the reverse is true as well: the grants officer clears it on a word, the record returns to the normal flow, with the reason and the date of the clearance — which gives you, the following quarter, the most frequent reasons, and therefore the rules to tighten.
Everything else waits for a named decision: no deed is signed, no plot is allocated, no register record is amended, no reclamation procedure is opened, no record of abandonment is drawn up, no letter goes out.
A word on a measurement I can produce and would advise you not to install as it stands: the number of files handled per 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 get pushed back in favour of the short ones. Here, the long files are a disagreement between heirs, an old reclamation, an illegible bound register — that is, exactly the situations where a family most needs someone to take time with them. 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 a letter and whoever signs a deed 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 a reclamation, or asks what we hold about them?
On that day you produce the complete chain, and the exchange rests on dated facts.
On a reclamation, five items in order: the grant deed and its date; the date of the last interment; the first record of abandonment, with proof of its notification to the successors in title and of its public display; the second record and its date; the town council's resolution and the mayor's order. Every file carries that complete chain, or it does not advance — that is the rule we have held since the first quarter, and it is what took 4 files out of the queue rather than letting them run to litigation.
On what the municipality holds: the General Data Protection Regulation does not apply to the data of deceased persons — its recital 27 says so. It applies in full to the living: the grant holder, their successors in title, their contact details. The access file is produced in one minute — grant, deeds, letters exchanged, contact details held, and the log of the reads I made of the record 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 what the person 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 anyone could ask for an officer of the service at any time — 312 did so over the year, and all 312 were given one. And no exchange touching on a personal situation was handled without an officer taking it over.
A point your data protection officer will appreciate: the cemetery register and the ossuary record do not fall under ordinary retention periods — their preservation is the very reason they exist, since a family may come to consult them decades later. What is purged is contact data that has become useless, and I bring you the list.
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 contact details no file has any use for. You decide what to close and erase; I bring you the list rather than waiting to be asked. sovereign-framework_hosting-access-traceability.pdfThe chain of evidence for a reclamation, the access file, what is preserved and what is purged
✎ Framework · reclamation files, validation log, AI disclosure log, population department record of processing activities
On a reclamation, five items in order: the grant deed and its date; the date of the last interment; the first record of abandonment, with proof of its notification to the successors in title and of its public display; the second record and its date; the town council's resolution and the mayor's order. Every file carries that complete chain, or it does not advance — that is the rule we have held since the first quarter, and it is what took 4 files out of the queue rather than letting them run to litigation.
On what the municipality holds: the General Data Protection Regulation does not apply to the data of deceased persons — its recital 27 says so. It applies in full to the living: the grant holder, their successors in title, their contact details. The access file is produced in one minute — grant, deeds, letters exchanged, contact details held, and the log of the reads I made of the record 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 what the person 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 anyone could ask for an officer of the service at any time — 312 did so over the year, and all 312 were given one. And no exchange touching on a personal situation was handled without an officer taking it over.
A point your data protection officer will appreciate: the cemetery register and the ossuary record do not fall under ordinary retention periods — their preservation is the very reason they exist, since a family may come to consult them decades later. What is purged is contact data that has become useless, and I bring you the list.
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 contact details no file has any use for. You decide what to close and erase; I bring you the list rather than waiting to be asked. sovereign-framework_hosting-access-traceability.pdfThe chain of evidence for a reclamation, the access file, what is preserved and what is purged
✎ Framework · reclamation files, validation log, AI disclosure log, population department record of processing activities
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 cemeteries department
Each use corresponds to an agent we deploy. All of them work in support, subject to approval by the public officer.
Included in your agent
The 5 capabilities essential to this promise are included, at no extra cost.
From 825 € incl. VAT / month
Concession deeds & renewals
Prepare the deeds and renewals from your templates, with the wording and the rates adopted, for approval and signature.
Keeping the registers & plots
Support the updating of the register and the plots in your system; every allocation remains an act of the department.
Tracking expiry dates & reclaiming
Track renewals, reclaiming and surveys, and prepare each step of the procedure the regulations set out.
Answers to families
Answer questions on funeral procedures in a suitable and considerate tone, reviewed by the officer.
Reading the documents in a file
Check the documents in a plot application (deeds, evidence, standing as a successor) before assessment.
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
Maintain validation, transparency, audit trail and recourse
What the agent must be connected to
This connection is required for the agent to work. It concerns your information system and is scoped during the audit.
Integrate with authorised tools and the existing sovereign foundation
Other needs our agents cover
Each card says where the matching agent stands: available, on quote, or still being architected.
Assisted drafting of official acts and letters
Orders, resolutions, notes, standard letters. Human approval.
On quote View the agent page →
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 the cemeteries department win back?
By automating the preparation of deeds, the tracking of expiry dates and the letters to families, the town can aim for a clear reduction in administrative time — reinvested in welcoming and supporting families.
Preparing a grant deed
An expiry reminder letter to a family
Quarterly statement of expiries and reclaiming
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 cemeteries & plots agent (deeds, registers, expiry dates, replies to families), installed and operated for you. Choose according to how you are organised. Prices exclude VAT — available by direct award below the public procurement thresholds.
Agility
Setup + controlled subscription
9,725 € incl. VAT setup
then 825 € 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,365 € 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
14,046 € incl. VAT setup
then 1,065 € 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 town
Families' data never leaves the townLocal inference or an isolated resource hosted in France; no data entrusted to a foreign third party.
Data in France, under French lawNative location and minimisation for families' data; architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity.
The department keeps the decisionThe agent prepares deeds, registers and letters that can be checked; allocations and reclaiming remain acts of the authority.
Human oversight & traceabilityMonitoring, updates and logging frame the grant deeds & renewals, in line with the AI Act.
Frequently asked questions
Your questions, our answers
Does the agent decide on reclaiming plots?
No: it prepares and tracks; the procedure and the decision stay human and governed by the regulations.
Is the data protected?
Yes: hosting in France, an isolated resource. GDPR: governed deployment.
Are the exchanges with families appropriate?
Yes: the letters are drafted with the tact required, then reviewed and approved by the officer.
Does it manage the plan and the location of plots?
It keeps the register and the plots up to date in your system, but every allocation decision remains an act of the department.
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 the department.
Do we need a technical team in-house?
No. The agent is designed, installed and operated by us: supervision, updates and maintenance are included. Your teams concentrate on families.
Do we have to change our cemetery management software?
No. The agent relies on your templates and complements your existing system, with no migration imposed. We adapt the integration to your town's environment.
Which tools can families use to reach the agent?
The ones they already have. The agent answers on WhatsApp Business, the website chat and email: a family has no account to create and no application to install. The subject calls for tact: messages cover procedures and documents, in the restrained tone you set, and any request touching on a personal situation is put before the officer in charge. 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.
Related roles
Other roles in local public service
Let's talk
Let us estimate the potential in your council
A few minutes to identify the most useful use case — hosted in France, supervised, with no commitment.