Skip to main content
CitadelAero

Every document, the same questions.

A review table asks the same questions of every document in a project, one row per document, each answer proposed and cited to its source.

Request a demo

Sample data. Wexmoor Air is a fictional operator. The app’s own template: “Manual compliance review”.

Ask every document the same questions.

Each column asks one question, and each document in the project is a row, answered from that document alone.

  • Templates

    Start from one the app ships with: a manual compliance review, a safety data analysis, or an AD/SB applicability review for the CAMO to confirm.

  • Columns you write

    Name a column and say what to ask of each document. Chuck drafts the question from its title, for you to edit.

  • Checked against the regulations

    Tick a column and each answer is given the provisions that govern the question, from your regulation libraries, and cites them. Leave it off for a fact read straight from the document, such as a date.

Every answer proposed and cited.

None of it is a compliance finding: the table sets out what each document shows against what the provision requires, and a competent person decides.

  • Proposed, for a person to confirm

    Each assessment comes back proposed, and the “Checked by / Date” column is left empty for them to sign.

  • Cited to the passage

    Each cell cites its source. Follow the citation and the document opens at the words it quoted.

  • Watch it run

    Cells fill as Chuck works through the table, and the header says where it has got to.

Take it further.

A finished table is a starting point: for a chat, for the next set of documents, or for your own records.

  • Export to Excel

    Download the table as an Excel workbook, with each cell’s sources as a comment.

  • Chats about the table

    Ask about the table in a chat that stays with it, beside every other chat about it.

  • Save as a workflow

    Save it as a workflow, to run again on the next set of documents.

How teams use review tables.

  • Manual compliance review

    A set of separate procedures, each read against the requirement it is meant to satisfy. For one whole manual read area by area, the gap analysis workflow does it in a chat.

  • Safety data analysis

    One row per safety case (occurrence and hazard reports, audit findings, MORs), the same fields recorded from each and reportability proposed. The rows feed the analysis report or a review-board pack.

  • AD/SB applicability review

    Airworthiness directives and service bulletins reviewed against the fleet, applicability proposed for the CAMO to decide.

More of Chuck

Chuck overview

See it against your own manuals.

We set Chuck up with the frameworks you operate under, and walk you through it on your own material.

Request a demo