Continuous compliance for in-house compliance managers
Move from audit-eve archaeology to a standing picture: what the manuals cover, where the gaps are, who owns each corrective action, and what changed in the regulations this month.
The compliance manager's core problem is that compliance decays silently. A manual revision changes a procedure but not its cross-references; a regulation is amended and the manual is not; a corrective action from the last audit quietly loses its owner when someone changes roles. None of it announces itself — it is discovered, usually by an inspector.
Navlyt turns that silent decay into visible state. Manuals stay mapped clause-by-clause to FAA 14 CFR Part 135 and Part 91 requirements, so coverage is a standing fact rather than an annual project. Gaps surface as findings with the manual's own text quoted as evidence. Accepted findings become corrective actions with owners and target dates — and an action past its date or without a plan is surfaced on the dashboard as a live exposure.
Regulatory changes arrive as a feed with effective dates and action-required flags, so 'did we respond to that rule change?' has an answer that isn't an email search.
A dashboard that tells the truth
Navlyt's dashboard reports what the underlying data supports — and labels what it doesn't. Open tasks reconcile to their overdue / due-soon breakdown. Medical tracking is labelled as medical tracking, not inflated into a 'crew currency' claim the data can't carry. Where a metric has limits, the limit is stated on the card.
- Open tasks with owners, and an oldest-overdue counter that won't let backlog hide
- Corrective actions: open count, past-target-date, and missing-plan flags
- Document lifecycle: the draft / in-review / approved split, visible daily
- Medical expiries flagged as current, expiring, or expired
Corrective actions that survive personnel changes
The corrective-action register lives in the system, not in a spreadsheet on someone's desktop. Each action carries the finding it came from — with its cited evidence — plus an owner, a target date, and a disposition history recorded server-side. When roles change, the register doesn't.
Regulatory change, triaged
Changes to the rules you operate under arrive as a feed showing the effective date — the date you must be compliant by, not just the date we noticed — and whether a response is still required. Creating a follow-up task from a change takes one click, and the system refuses to create duplicates.
Audit trail by construction
Review attributions are owned by the server: who accepted a finding and when is recorded at the database layer and cannot be edited from the browser. Role-based permissions govern who can upload, approve, delete, or review — so the trail your auditor reads is the trail that actually happened.
Frequently asked questions
How is this different from a task manager or spreadsheet?
Three ways: the tasks are connected to cited regulatory evidence rather than free text; the audit trail is server-owned rather than editable; and coverage against Part 135 is computed from your actual manuals rather than asserted. A spreadsheet can record intentions — Navlyt records state.
Can I assign findings to people outside the compliance team?
Yes. Corrective actions carry owners from anyone in your operator workspace, with role-based permissions controlling what each person can change. Pilots and maintenance staff can hold actions without being able to alter the register's history.
What does the regulatory changes page cover?
A curated set of changes relevant to FAA Part 135 operations, each with its effective date and an action-required flag your team clears by responding. It is not yet a live feed and does not send alerts. EASA and Transport Canada are on the roadmap and labelled as such.
Does the AI ever mark something compliant on its own?
No. The AI proposes; people disposition. Findings are suggestions until a qualified person accepts or dismisses them, and the software never reports compliance it cannot support — that principle is applied to our own dashboard as strictly as to your manuals.
How do I show management the state of compliance?
The dashboard is the live answer; PDF evidence reports are the briefable one. Both draw from the same data — open findings, corrective actions and their dates, document lifecycle, and crew records.
What about SMS?
SMS program support is on the roadmap — with the FAA's Part 135 SMS mandate approaching, we're building the mapping model deliberately rather than forcing the prescriptive-regulation shape onto it. The corrective-action and document-control workflow already covers much of the ground SMS auditors examine.
Related reading
Replace audit-eve archaeology with standing state
Bring your manuals to a 30-minute demo and leave with a live gap register — owners, dates, and cited evidence included.