Products
Agentic products for the work an airport does every day.
Four domains, each served by a small team of agents with named roles. Not chatbots: agents with an input, an output, a warrant, and a person who signs. The same engine underneath, configured to your procedures.
01 · Reporting
Safety & security occurrence reporting
Two regimes, one job: turn what happened on the apron, at the checkpoint or in the terminal into a report in the right taxonomy, by the right deadline, signed by the right person.
| Safety | Reg. (EU) 376/2014 — mandatory occurrence reporting within 72 hours of becoming aware; analysis and follow-up by the organisation (art. 4(7), art. 13). |
| Security | Reg. (EU) 2026/247 — 24 h / 72 h / monthly by impact, common template (App. IV) and classification (App. V), national process from 1 January 2028 (point 19). |
Reporter
Drafts, classifies, computes the deadline, routes
Reads shift logs, radio notes, emails and alarm exports; drafts the report in your template or the EU one; proposes the class; attaches the sources; sends it to the responsible person. Never files with the authority itself.
Analyst
Prepares the follow-up
Groups related occurrences, drafts the analysis and the corrective-action proposal your safety or security manager will decide on, and keeps the register of what was reported, when, and what came of it.
Delivered
In your systems
A report ready to sign, a follow-up draft, a reporting register — in your document tool, your mailbox or your safety software, with the ledger behind each one.
02 · Compliance
Inspections, audits and registers
The visit is short; the preparation is not. The evidence exists — spread across training files, equipment logs, badge registers and previous findings. The register should be right every day, not the week before.
| Security | Reg. (EC) 300/2008 and its implementing rules — audits, inspections and tests under the national quality control programme; staff recruitment, training and certification; access control. |
| Aerodrome | EASA aerodrome rules (Reg. (EU) 139/2014) — oversight of the certified aerodrome, its safety management system and its procedures. |
Auditor
Assembles the evidence pack, lists the gaps
Builds the folder the way the inspector will ask for it; produces the gap register — expired, missing, inconsistent — weeks before the visit; drafts the corrective action plan. Never edits an original or closes a finding.
Registrar
Keeps the register of people
Who is trained, certified and badged for what, until when — maintained from your rosters, training records and badge files; expiry lists per team early enough to book training; complete application files for the issuing office. Never issues or revokes anything.
Delivered
Before the visit
An evidence folder, a gap register, a draft action plan, an up-to-date people register — in your shared drive and your spreadsheets, every document pointing to its source.
03 · Operations
Airside records and work orders
Movement areas are inspected, screening equipment is tested, shifts hand over, tickets are opened with maintenance and IT. Each produces a record — and each missing record is a question during the next audit.
| Inputs | Inspection logs, FOD and lighting reports, equipment daily-test exports, handover notes, open tickets, maintenance calendars, A-CDM milestones. |
| Rules | Your aerodrome manual and procedures; EASA aerodrome rules for the monitoring and inspection of the movement area; your security programme for equipment tests. |
Clerk
Reconciles what was due with what was logged
Every morning, per area, per lane, per device: done, missing, inconsistent. Drafts the work order or the ticket in your queue — ServiceNow, Jira, your CMMS or a mailbox — with the log excerpt attached. Never closes a ticket or reports a test as done without a record.
Dispatcher
Keeps the handover and the exceptions list
Compiles the shift handover from the records rather than from memory; flags turnaround and milestone exceptions to the duty manager with the data behind them; drafts the daily operations log for review.
Delivered
Same morning
A daily exceptions list, drafted work orders and tickets, a complete handover, a daily log — in the systems your maintenance and operations teams already open first thing.
04 · Passengers & neighbours
Assistance requests and complaints
Two streams that never stop: assistance requests from passengers with reduced mobility, and complaints from the people who live around the airport. Both need a trace, a deadline and a reply someone can stand behind.
| Assistance | Reg. (EC) 1107/2006 — the airport managing body is responsible for assistance to disabled persons and persons with reduced mobility, and sets quality standards for it. |
| Neighbours | Noise maps, action plans and complaint handling under your environmental obligations and local commitments; replies grounded in the flight and noise data you already publish. |
Correspondent
Classifies, drafts, tracks
Reads requests and complaints from your mailbox or portal; classifies them; drafts the reply from your procedures and published data; tracks each case against its deadline and quality standard. Never sends anything itself — a person does.
Reporter
Produces the periodic reports
Monthly and annual assistance and complaint reports compiled from the case register, with every figure traceable to the cases behind it.
Delivered
A case register and drafts to send
In your ticketing tool or mailbox: replies ready for approval, a live register of cases and deadlines, periodic reports your management and your authority can check line by line.
The roles, and what every one of them is made of.
Six roles, reused across the four domains. Each one is a written warrant, defined inputs and outputs, and a named person it hands over to.
| Role | Reads | Does | Never |
|---|---|---|---|
| Reporter | logs, notes, emails, alarm exports | drafts the report, proposes the class, computes the deadline, routes for signature | files with an authority; changes what a witness wrote |
| Analyst | reported occurrences, previous analyses | groups, drafts the analysis and the corrective-action proposal | decides the action; closes a case |
| Auditor | programmes, findings, records | assembles the evidence pack, lists gaps, drafts the action plan | edits an original; marks a finding closed |
| Registrar | rosters, training records, badge files | maintains the register, flags expiries, checks files for completeness | issues, extends or revokes anything |
| Clerk · Dispatcher | inspection and test logs, handovers, tickets, milestones | reconciles, drafts work orders and tickets, compiles handovers and exceptions | closes a ticket; reports a test done without a record |
| Correspondent | requests, complaints, published data | classifies, drafts replies, tracks deadlines and standards | sends anything itself |
Woken by work, not by a timer
A coordinator routes new work to the right role, tracks dependencies, and escalates to your named contact when something is blocked. Anything that leaves the organisation, changes a record of consequence, or falls outside the warrant goes to a person — with the agent’s reasoning attached.
Not in the four domains? We build the role.
A local reporting rule, a contractor onboarding, a recurring return to an authority. If it is written down, repeated, and someone can say what “done” looks like, we build the agent around it — with the same warrant and ledger. How the pilot runs