the report gets filedwhere there is no signal.
The places safety reports are made are the places with no bars: a stand, a hangar, a cargo bay, a line station. eAviora Field is the iOS app for those places. It is not the website in a wrapper, and it is not a companion product. It is the same platform, on a phone.
The report that never gets filed.
Anything that asks an operator to remember, retype, or come back later is a report that never gets made. So the app assumes no signal and treats a connection as the exception.
One path, signal or none. Every capture goes through the same queue whether you have bars or not. A separate online path would be a second failure mode, and the rare one is the one that loses a report.
Drafts save themselves. The report writes to the device as you type. There is no Save button because there should not be one, and a backgrounded app that iOS kills keeps the work.
A queued report is never dropped. Caches are cleared on an app update. The outbox and the drafts are not, because they hold reports that exist nowhere else yet.
One device, one operator. The local database is per user and is wiped on sign out, so a shared crew room phone never leaves one person’s queued reports readable by the next.
Five surfaces,
one duty day.
Not a cut-down reporting form. The work an operator actually has on them, in the order a shift hands it to them.
What this person owes today, most urgent first, with overdue and due-today counted.
File against the airline’s own report types, the ones configured on the server, with their own icons.
The audits this inspector can work, downloaded on purpose before walking into a hangar.
Controlled documents on the device, with the acknowledgement recorded against the revision.
Who is signed in, what is still waiting to sync, and the way out of a shared device.
One hand free. Ninety seconds of attention.
An operator standing next to the thing they are describing is the best source the safety system will ever get, and the worst place to ask for typing.
Photographs ride the report. A photo is copied out of the picker at the moment it is picked, so it survives the phone clearing its own cache, and it follows the report as evidence.
Say it, then walk away. A voice memo attaches the same way. One hand free and ninety seconds of attention is the real constraint on a stand.
Structure it when you have signal. The narrative can be turned into fields, online only, and it writes nothing on its own: it fills what you left empty and marks it suggested until you edit it.
Filed on a stand. Read at a desk.
A companion app is a second system with a second set of words and a second way to be wrong. This is the same database, the same procedures and the same vocabulary, so an hour later the report is not a copy of the one that was filed. It is the one that was filed.
The same procedures, not a mobile API. Every write the phone makes calls the procedure the web calls. There is no mobile API, no mobile table and no mobile column to fall out of step.
The same words. One vocabulary file defines every label an operator reads and is copied into the app byte for byte, so a reporting mode means the same thing on a stand and at a desk.
The server answer always wins. A queued acknowledgement only fills the gap between capture and sync. The record decides, so the phone cannot show work as outstanding after somebody closed it on the web.
The stand is the hard part.
You have seen where the reports come from. The next leg is where you evaluate the platform they land in: the comparison, the questions, the trust answers.