What to Keep in a Personal Aviation Workbench

On your last day, the email account closes. The quality system login stops working. The audit tool, the document control system, the SMS platform and the training portal all stay with the company.

That is correct. Company systems belong to the company.

But a lot of what you learned while working inside them was never company property: how to sample evidence, which regulation references you kept returning to, how you structure a finding, when your EWIS refresher is due. If none of that has a home outside the employer's software, every new role starts with a quiet reset.

The fix is not to copy the company system into a private folder. It is to keep two layers apart on purpose, and to know which one each piece of work belongs to.

Two knowledge layers: yours and the organisation's

Every aviation professional works across two layers.

The organisational layer holds company records, controlled documents, internal reports, customer data, audit files, occurrence records, commercial material and approved procedures. It belongs in company systems, where access, retention and approval are controlled.

The personal professional layer holds your own learning, study notes, public regulation bookmarks, certificate reminders, generic checklists, non-confidential lessons, career records and questions you want to follow up. It should travel with you.

Most people do not manage that split deliberately. Either everything lives inside company tools, where the personal learning is trapped, or the personal layer is scattered across email, PDFs, screenshots, note apps and memory, where it is hard to find and easy to mix with company material.

A personal workbench gives the second layer a proper home. What that workbench is, and why it travels, is in what a personal aviation workbench is. The sections below are what usually belongs in it. The last section is what never does.

Certificates and qualifications

Certificates are the clearest case. A licence, a type rating, human factors, EWIS, fuel tank safety, dangerous goods, a medical, an internal authorisation: each one has a date that matters and evidence that proves it.

Keep your personal view of each item:

• certificate or qualification name;
• issuing body or training provider;
• issue date and expiry or next-due date;
• renewal window and reminder dates;
• where the evidence is held;
• notes on scope or limitations.

This does not replace the company training record. The company record remains official for company approvals and authorisations. Your view exists so you are never surprised by an expiry, whichever employer or contract you are on. The certificate tracking article covers what a good record captures.

Public regulation bookmarks

Most professionals return to the same regulatory areas again and again: Part-145, Part-CAMO, Part-M, Part-66, Air OPS, the AMC and GM behind them.

The key word is public. Official EASA pages, Easy Access Rules and publicly available guidance can sit in a personal knowledge system. What makes a bookmark useful is a note on why it matters:

• "useful for competence review";
• "check before audit planning";
• "relevant to certifying staff privileges";
• "good source for maintenance programme context";
• "verify current version before use."

A bookmark is not a check. Regulation changes, and the source must be confirmed as current before it supports professional work.

Glossary and training notes

Aviation runs on terms people use daily but rarely define: accountable manager, certifying staff, support staff, continuing airworthiness, airworthiness review, finding, root cause, corrective action, containment, AMC, GM, MEL, AMP, CRS.

A personal glossary is a learning layer, not an official definition. Link each entry to a public source where you can, and mark your own explanation as yours.

Training notes fit here too: course summaries, study notes, revision points and questions for later. Two boundaries apply. Do not store course material the provider has not allowed you to keep. Do not upload internal slides or company-specific training records without permission. Your notes should capture what you learned, not reproduce what you were shown.

Non-confidential templates and recurring tasks

Templates are useful when they are generic and yours:

• audit preparation checklist;
• meeting summary outline;
• regulation review table;
• finding draft structure;
• certificate renewal checklist;
• procedure review questions;
• personal handover checklist;
• lessons-learned format.

These are thinking aids, not copies of controlled company forms. When the work becomes official, it moves into the approved company form or system.

Recurring personal tasks keep the whole thing alive. Review certificate status monthly. Check upcoming training needs. Refresh study notes. Prepare questions before an audit. Clean out old notes. Without tasks, a workbench is storage. With them, it prompts you.

Lessons learned and reusable thinking

This is the most valuable layer, and the one most people lose.

A compliance manager does not only complete an audit. They learn how to sample evidence without drowning the auditee, how to keep a finding factual, how to separate an observation from a non-compliance, and how to follow a CAP without quietly accepting weak root cause analysis.

A CAMO professional does not only process one continuing-airworthiness task. They build patterns around AMP changes, reliability signals, deferred defects, records reviews, supplier interfaces and the point where a neat spreadsheet stops being adequate evidence.

A Part-145 certifying staff member does not only close a work order. They learn practical judgement around CRS wording, tooling, parts traceability, maintenance data, human factors, shift handover and authorisation limits. A trainer learns which parts of an OM or MOE briefing actually stick and which questions expose weak understanding.

Capture the lesson while it is fresh, and write it so it carries no company detail:

• "separate evidence from opinion when drafting findings";
• "check the source before quoting a requirement";
• "write meeting actions with owner and due date";
• "do not assume old procedure wording is current";
• "mark assumptions clearly in draft reports";
• "ask whether the issue is training, access or process before calling it competence."

Company names, record numbers, aircraft registrations and customer details stay out. The lesson generalises; the case does not leave. That is what makes it portable and safe.

Career profile and AI preferences

Aviation careers move between operators, MROs, CAMOs, training organisations, contracts and countries. A career profile helps you remember what you can do and what you need to maintain:

• roles held and aircraft types worked on;
• training completed and approvals held;
• audit experience and systems used;
• professional goals, renewal priorities and skills to develop.

It is a personal map for interviews, renewals and development planning, not a copy of company HR records.

If your workbench includes an AI assistant, your working preferences belong here too:

• use plain English;
• separate facts from assumptions;
• ask for sources before drafting compliance text;
• remind me when a task may belong in a company system;
• show uncertainty;
• do not treat personal notes as official sources;
• stop before anything needs approval.

These instructions make the assistant more useful and keep your professional boundaries visible every time it drafts something.

What must stay in company systems

This section matters most. A personal workbench must never become a way to remove company information from the company. In aviation, records, safety information, customer data and controlled documents can carry legal, regulatory and contractual obligations.

Unless you have explicit permission and a lawful reason to hold it elsewhere, the following stays in company systems:

• controlled company procedures and manuals;
• audit records and finding files;
• occurrence reports and safety reports;
• internal investigations;
• aircraft records and official evidence used for compliance;
• customer, supplier or aircraft-specific confidential data;
• proprietary forms, templates and manuals;
• confidential meeting notes and internal management decisions;
• commercially or security-sensitive information;
• personal data about colleagues, customers or anyone else.

If in doubt, keep it out.

Scattered notes are the bigger risk here, not a well-organised personal layer. When knowledge lives in email, WhatsApp, downloads and screenshots, it is easy to mix personal and company material without noticing, or to reuse an old note without checking whether the rule changed. A deliberate personal workbench makes the question explicit: is this mine, or the organisation's?

The same discipline applies to AI tools. Pasting company records into a personal chat subscription moves them out of company control just as surely as copying files. The shadow AI article covers that side.

How Avioverse organises it

Avioverse is a personal workbench for individual aviation professionals in an EASA environment. It works beside company systems of record; it is not the company QMS, SMS, document control or approved exposition.

The categories above map onto it like this:

• Certificates become tracked records with an issuer, last completion date and validity period. Avioverse works out the next due date, and a recurring item creates a linked task, so the reminder appears in Tasks and Calendar. You can attach the certificate file and let AI read it to fill in the fields for you to confirm.
• Regulation bookmarks come from the built-in EASA regulation library, which shows version and status information. Sources you find can be saved, with your own notes, into Brain.
• Glossary entries, training notes, lessons and career notes live in Brain, a personal knowledge base on Pro that you and Metis, the assistant, can both edit. Metis can recall it across chats.
• Recurring personal work becomes tasks with reminders, or a reusable procedure you run each time.
• AI preferences are kept by Metis's memory on Pro, so you do not re-explain how you work in every conversation.

The boundary is built in too. When you work with colleagues in a team workspace, that work belongs to the team. Your personal workspace stays with your account. Whatever Metis drafts is a draft: you review it, and official work goes into the correct company system.

Keep what makes you better, leave what belongs to them

Keep certificates, reminders, public source bookmarks, glossary notes, generic templates, training notes, lessons learned, personal tasks and career information.

Leave company records, controlled procedures, safety data and official evidence in company systems.

You keep your professional continuity. The organisation keeps control of its official records. Each new role then starts from what you already know.