Employee records: documents filed, deadlines met
A complete employee record is both an obligation and a peace of mind: contract, variations, medical check-ups, authorisations, training. Your agent files each document received in the right place, flags what is missing against your internal rules and tracks renewal dates. Hosted in France: your employees' data stays with you. The HR team decides what to do about each flag.
Updated on
For each: the document expected, the rule that requires it and the date it has been outstanding since.
Four concern an authorisation whose renewal date is approaching: they are put at the top.
🔗 Sourced · employee records and internal rules
They are put to the HR team before sending: a letter to staff commits the employer.
✎ Action · requests to read over, sending decided by you
A Blue Lemon Agent HR document agent files the documents in employee records, flags those missing against your internal rules and tracks renewal dates — medical check-ups, authorisations, mandatory training. Requests for documents are prepared and read over before sending. It runs on local inference or is hosted in France: your employees' data stays with you, architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity.
These figures describe our offer, not results measured at a client. How large the gain is on your number of employees and documents tracked is confirmed by a pilot.
What does an AI agent bring to your employee records?
A complete record and deadlines seen in advance mean time given back to the HR team and compliance kept without a last-minute scramble.
! The issue
Keeping an employee record rests on two routine acts: filing the document received and checking what is missing. Multiplied by the headcount, they take up a real share of HR time. The agent takes them on, drawing on your internal rules, and sets out renewal dates before they arrive.
✓ Our answer
The HR team sees at a glance the records to complete, the rule that requires it and the deadlines approaching. Requests for documents are prepared but read over: a letter to staff commits the employer. Local inference or an isolated resource hosted in France: your employees' data, among the most sensitive the company holds, is entrusted to no third party.
Your employees' personal data: sovereignty & compliance
Employee records concentrate personal data, sometimes health data. Here is how the architecture of our agents protects it.
Local inference
The agent can run on a machine belonging to your organisation: no document and no employee data leaves the network.
Hosting in France
Otherwise, a dedicated and isolated resource hosted in France, under French law — your employee records and your mandatory documents: processing and access within the European Union targeted by the architecture.
Reduced extraterritorial exposure
For your employees' personal 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.
Isolated resource
No pooling: an environment strictly dedicated to your company and its internal rules.
Every flag tied to a rule
Any document flagged as missing refers back to the internal rule that requires it; encryption, role-based access, logging of consultations and purging at the retention periods you set.
AI Act: governed deployment
The agent is strictly in support; no letter is sent and no decision about an employee is taken; 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.
- 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.
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.
· Forty-one contract amendments carry no employee signature. Eleven concern a change of pay.
· Thirty-four medical documents sit in ordinary personnel files, reachable by seven people. I restricted them this morning; I opened none of them.
· Nine disciplinary items exceed the retention period set by your note of 03/03/2025, the oldest by six years.
· Two hundred and twelve documents are filed as "miscellaneous". I could not say what they were, and I did not guess. morning-watch_4-flags.pdf34 documents restricted · 0 opened
⛓ Source · 214 personnel files, procedure note of 03/03/2025, access rights
What I read: the file name, the issuer where it appears in the letterhead, the form type, and the folder it sits in. A fitness certificate carries a heading, a sick note has a known layout, a doctor's letter has a letterhead.
What stays closed, and it is what makes the filing usable: the body of the document. A reason for absence, a fitness restriction, a diagnosis enter no index — the 34 items are filed, named and dated without a single health datum changing hands.
What I did this morning, on my own: I brought their access from seven people down to those your note designates. It is the only action I take without asking, and it always goes the same way: less access.
What goes out prepared and waits for your click: opening an access, moving a document out of the file, deleting it. The request arrives written — who, which file, what reason, until when — and it is approved in one click: the 12 requests this month were each settled in under two hours. Restricting wrongly is repaired in a minute; opening wrongly is not — the document has been seen, and that is the only reason that particular click is yours.
What I supply: the list of 34, by type and by file, without one line of their content. 34-documents_restricted-unopened.pdf7 accesses → those the note designates
⛓ Source · headings and letterheads, note of 03/03/2025, access log
Routing follows what can be repaired: an unsigned amendment goes to HR, and nobody else — it is a contractual matter; a misfiled medical document to HR, with the restriction already in place; a disciplinary item beyond its period to the same person, never to the employee's manager; a document I could not classify to whoever files, marked "undetermined".
With a chase: 48 h on over-wide access, 7 days on the rest. Then a monthly summary: by document type and by gap, never by employee.
What is already secured this morning: 34 medical documents have gone from seven readers to those your note designates, without one of them being opened; 41 unsigned amendments are out of the shadows, 11 of them on pay; 9 disciplinary items beyond their retention period are dated and listed. Across 214 files, that is a completeness check that no longer happens file by file, but continuously.
Sovereignty here is a setting, not a promise: access is opened by role, logged, withdrawn on a word, and nothing leaves the company — local inference or an isolated resource hosted in France. The only move I make on my own always goes the same way: less access, and it is undone in a minute.
What follows is yours, and it is ready: chasing the 41 signatures, refiling the 212 "miscellaneous", purging the 9 items beyond their retention period — that last one cannot be undone, so it waits for a mandate that names the 9 items, one by one. On a written, capped, dated mandate, revocable on a word, the rest is carried out within minutes, with the log to show for it, and your HR team reads one statement instead of reopening 214 files.
✎ Framework · restrict alone, never open alone, never delete
Across 212 personnel files, your note requires nine documents per employee — fourteen for posts requiring an authorisation. There are 147 missing documents, and they are very unevenly spread:
· 61 medical examination certificates absent from the file, 38 of them for employees you told me had attended: this is the document that exists and never reaches the file;
· 34 proofs of qualification required by article 4 of your note;
· 28 mandatory training certificates for posts that require them;
· 19 bank details predating the last declared change;
· 5 signed copies of the staff handbook.
Every flag carries the rule that grounds it, quoted — "procedure note of 09/01, article 4, paragraph 2" — and the person who holds the document. A gap with no rule quoted gets argued about for six months; a gap with its rule is closed in a week.
What is not counted as missing: 23 documents are present but illegible or unsigned. They are counted separately — asking again for a document is not the same errand as getting the one you already have signed.
✎ Framework · missing documents against your written procedure, rule quoted
What falls due over the next six months, in date order:
· 14 electrical authorisations expire, 3 of them within 30 days. Those block an assignment the day they lapse — the one case where a renewal cannot be caught up afterwards;
· 29 periodic medical examinations, 6 of them already more than two months overdue;
· 17 mandatory training courses to retake, 9 of which concern the same team and can be grouped into one session — 4 training days saved if you group them, and the grouping calendar is already proposed.
Reminders go out at 90, 45 and 15 days, to the HR manager and the line manager, never to the employee directly — that is your rule, not mine. Each reminder carries the expiry date, the source document and the cycle that sets it.
What the tracking caught over twelve months: no authorisation expired without a renewal under way, against 7 the previous year, and two assignments postponed rather than cancelled.
A figure that does not suit me: 11 due dates were calculated from the wrong date, all medical examinations whose file carried the appointment date rather than the certificate date. The certificate date now overrides any other date in the file, and all 11 were recalculated — 3 were in fact overdue and went out as reminders the same day. And nothing is deleted in the process: an expired document stays on file, it only changes state.
⛓ Sourced · dates on the file documents, renewal cycles from your note
What I record: 41 contract amendments in the files, with no employee signature. Eleven concern pay, fourteen working hours, sixteen place or duties.
What I do not conclude: that the employees did not accept. Agreement may have been given otherwise — by email, by a signed copy filed elsewhere, or by performance itself. I see a file, not a consent.
What makes the eleven more urgent: a pay change applied for months is harder to regularise the longer it runs, and it is the one case where time makes things worse.
What I supply: for each, the amendment's date, the date from which it was applied in payroll — where I can align them — and the absence of a signature in the file. Nothing else.
What is left to HR, and they come to it on a complete file: the letter itself. A request for a retrospective signature is an act of the company, and how it is worded matters more than the fact of sending it — starting with the eleven that touch pay, where every month that passes makes regularisation heavier. 41-amendments_11-about-pay.pdfWhat the file proves · what it does not
⛓ Source · 41 amendments, payroll start dates, personnel files
What I do when I recognise a document: I file it under your filing plan's heading, with the reason for my decision — the title, the letterhead, the layout.
What I do when I do not recognise it: I leave it where it is and record it as "undetermined", with whatever I could read of its title.
Why I do not pick the most likely heading: because a misfiled document is more dangerous than an unfiled one. An unfiled one is visible and gets handled; a misfiled one disappears into a heading nobody will search, and there it takes on that heading's access rights.
What I saw in the 212, without opening them: 103 have only a technical file name — a scan number. About those I can say nothing at all, and I say so rather than propose a heading.
What I propose: a naming rule at the point of deposit. It is upstream that this is settled, not in my filing. 212-unfiled_103-unreadable.pdfUnfiled gets handled · misfiled disappears
⛓ Source · 212 documents, filing plan, titles recorded
What I record: nine items exceed the period set by your note of 03/03/2025, one of them by six years. I rely on your note and quote no article of law: if the law provides a different period, the law prevails, and that check belongs to you.
Why I do not delete them, though that is exactly what should happen: because a deletion cannot be recovered. If my reading of a date is wrong, or an item relates to a live procedure I cannot see, it is gone — and nobody will know it existed.
What I do instead: I flag them, one at a time, with the date on the item and the rule from your note, to HR.
What I also do, and can do alone: I restrict their access — as with the medical documents, and for the same reason. Restricting is reversible, deleting is not.
What that gives: an item that should no longer weigh stops weighing, and it still exists until somebody decides. 9-items_restricted-not-deleted.pdfRestricting is reversible · deleting is not
⛓ Source · note of 03/03/2025, dates carried on the items
What I pass to HR: the list of nine, with the employee concerned, because an item cannot be handled without knowing which file it comes from.
What the rest of the company receives: the count, and nothing else. The monthly summary reads "nine items out of period", without the files — neither the employee's manager nor their future manager reads a name in it, and that is what lets it circulate every month instead of staying in the safe.
Why this precaution precisely here: a disciplinary item past its period is an item that must no longer have effect. Naming it to a manager would put it back in circulation at the exact moment it was meant to stop existing. That would be the opposite of the point.
And the question that will come one day, "has this employee ever been disciplined": it gets the same answer for every employee, whether an item exists or not — that is the only form that says nothing; an "I cannot answer" kept for some would already have answered. The ground is not caution: article L.1332-5 of the French labour code forbids relying on a sanction more than three years old in support of a new one. And what is lawful, I have already done: for the HR manager, every disciplinary item carries its date, its computed period of effect and the exact day it stops counting — the nine out of period are identified, and one click takes them out of the active file. Same work, done on the right side of the rule. who-gets-what.pdf1 recipient · 0 named summary
✎ Framework · no answer to "have they ever been disciplined"
If I restrict wrongly: somebody can no longer find a document, says so, and access is restored in a minute. The cost is an inconvenience.
If I open wrongly: the document has been seen. Closing the access again does not undo the reading, and on a medical or disciplinary document that is exactly what cannot be recovered.
What that gives as a rule: I can place a restriction alone, always flagging it the same day. I never lift a restriction alone, not even one I placed myself, not even where I find I was wrong.
That last point deserves saying: if I discover I restricted wrongly, I flag it, I do not correct it. An agent that can undo its own restrictions can undo any of them, and it then suffices to convince it that it was wrong.
Over twelve months: 61 restrictions placed, 9 lifted after review. All nine were lifted by a person. 61-placed_9-lifted.pdf9 lifted, 9 by a person
✎ Framework · restrict alone, never lift alone — not even its own
What is kept: each document's type and the reason for its filing — the title, the letterhead, the layout —, gaps flagged and their outcome, restrictions placed, by whom and when, and undetermined documents.
What is not kept: no document content, no extract, no summary, no medical element, including a title that would state its precise nature, no disciplinary history per employee, and no count of documents per employee.
The last is less obvious than the others: counting the documents in a file produces an indicator that looks like a story. A thick file says nothing — except that somebody has been here a long time, or has asked for a lot.
What the monthly summary contains: unsigned amendments, misfiled documents by type, out-of-period items as a count and without the files, and undetermined documents. Four indicators about filing, none about people. what-is-kept.pdf4 items kept · 6 impossible
✎ Framework · retention periods to be set by the company
Your case is not here? That is exactly what a 15-minute conversation is for. Book the free audit →
What does the agent actually do?
One agent, the whole document cycle of an employee record. All these uses work in support, subject to your approval.
Filing the documents
Puts each document received in its place in the record concerned.
Missing documents
Flags what is missing against your internal rules, with the rule cited.
Renewal dates
Tracks medical check-ups, authorisations and mandatory training.
File and index HR documents
To extract the data from the documents received, a dedicated document agent completes the picture.
Need to go further?
These agents handle a different business process, with their own owner and their own price. They are added to this one.
Everyday HR questions
For leave, payroll and formalities, a dedicated HR agent takes them on.
HR assistant (leave, payroll — everyday questions) from 623 € excl. VAT / month HR questions →Internal training
For practising procedures, a dedicated training agent takes over.
Internal training agent (tutor, quizzes) from 541 € excl. VAT / month Internal training →In 15 minutes we identify the most relevant agent — without oversizing the project.
How much time can an HR team give back to people?
By taking on the filing and the checking, the effort shifts towards supporting employees. How large the gain is depends on your volume and remains to be confirmed by a pilot.
The stages of your AI agent project
Audit & scoping
15 minutes to target the use case with the best return.
Quote or direct sign-up
A catalogue offer is bought online; a specific need gets a costed quote.
Design
We design the agent and its guardrails.
Integration & testing
We connect your tools to the agent, which is itself hosted in France.
Rollout
Going live and training your team.
Operation
Continuous supervision and improvement.
One package, one agent
An HR document agent (filing, completeness, deadlines), installed and operated for you.
Setup + controlled subscription
- Installation, configuration and training for your teams
- Operation, human oversight, updates and support
- Sovereign hosting in France, a dedicated and isolated resource
All inclusive, no setup fee
- Setup included (installation, configuration, training)
- Operation, human oversight, updates and support
- Sovereign hosting in France, managed end to end
On site, you own it
- Hardware installed on your premises (you own it)
- French / European AI models run locally
- Secure remote maintenance (Pro support included)
Four guarantees that matter to your employee records
Related resources
Your questions, our answers
Does the agent take decisions about an employee?
What is the list of expected documents based on?
How are health documents handled?
How long are the documents kept?
Is our employees' data protected?
How long does it take to deploy this agent?
Other agents for HR
Let's size up the potential in your employee records
15 minutes to frame your headcount and your internal rules — hosted in France, supervised, with no commitment.