Many parties.
One record.
One handover.

Inspections, findings, evidence, records, and responsibility. Shared across every organization involved in the project.

Shared record
Clear responsibility
Portable closeout

Replace the chain of files with a controlled record.

Aviatus is the working record used by the organizations responsible for getting an aircraft through inspection and handover.

Bring the starting point with you.

Existing lists can become the project baseline. Records and evidence then stay attached to the work instead of scattering across tools.

Work the same record together.

Authorized organizations contribute to the same project record. Responsibility and history stay visible.

Keep context with the finding.

Discussion, evidence, ownership, and status remain connected to the item that created them.

Close the project. Keep the record.

The record can be packaged at closeout instead of becoming useful only while the subscription and project remain active.

One line from intake to handover.

The project gains detail as the work happens. There is no reconstruction exercise at the end.

  1. 01ScopeProject + assets
  2. 02ConnectAuthorized parties
  3. 03ExecuteFindings + evidence
  4. 04ResolveResponsibility + closure
  5. 05HandoverFinal project record

Airframes and components are first-class assets.

Same operating model for redelivery, delivery acceptance, mid-term checks, pre-purchase diligence, engine transitions, component transitions, and audit work.

Findings keep a durable identity.

Items keep a durable identity through the project, so the conversation stays on the finding.

Your project should remain useful after Aviatus is no longer part of it.

Inspections end. Leases end. Vendors change. The Final Project Archive is the record you keep.

Final project archive

At closeout the project is packaged as a self-contained archive. The work, its full history, and the evidence and records Aviatus holds are written out as files you keep and can open without us.

Records linked in from Box travel as links and metadata, and still depend on your access to Box. The archive labels which files Aviatus holds and which remain Box links.

Built for where the aircraft actually is.

The mobile app is designed for inspection work away from a desk: capture findings, evidence, and updates in the field, then synchronize when connectivity returns.

Send a project to your phone

Pull a project down before you head out to the aircraft, and keep working it when connectivity drops.

Evidence in context

Capture photos and supporting material where the finding is raised.

On-device voice input

Dictate technical notes on the device.

Shared project access

Authorized external organizations can work on their assigned projects from mobile.

Get the app

Smartsheet in. Box in place. Evidence in Aviatus.

Bring an existing list in once. Browse governed records where they live. Keep inspection evidence with the finding.

SmartsheetBring an existing sheet in once, as the project's starting point.
BoxBrowse aircraft records in place. Each viewer connects their own Box account, so permissions follow Box, and records access stays read-only.
Aviatus storageInspection evidence is held here.

One operating model across technical engagements.

Redelivery Delivery acceptance Mid-term checks Pre-purchase diligence Technical audits Engine transitions Component transitions

Run the inspection.
Keep the record.

Bring the project, the assigned parties, the findings, and the evidence into one controlled operational record.