For many Part 147 maintenance training organisations, the question bank started as a spreadsheet. Maybe an Excel file with columns for the question text, the four answer choices, the correct answer, and the Part 66 module number. At first, it worked well enough.
But then the organisation grew. More modules, more instructors contributing questions, more exam sittings per year. And suddenly that spreadsheet became a liability — not just operationally, but from a regulatory compliance perspective.
This article examines why spreadsheet-based question bank management creates risk for Part 147 MTOs, and what a purpose-built system should offer instead.
The Spreadsheet Problem — Five Failure Modes
1. No Module-Level Tagging Structure
EASA Part 66 defines 13 core modules for basic knowledge examinations, each with detailed sub-topics at defined knowledge levels (1, 2, or 3). A spreadsheet can store module numbers, but it cannot enforce a structured taxonomy that maps questions to the correct sub-topic and knowledge level. Without this structure, you cannot reliably verify that your exams cover the full syllabus.
2. No Version Control
When multiple instructors contribute questions to a shared spreadsheet, version control becomes impossible. Which version is current? Who changed what, and when? Were deleted questions archived or lost? NAA inspectors expect to see an auditable history of question bank changes — something a spreadsheet fundamentally cannot provide.
3. No Review Cycle Tracking
Every question in your bank should be periodically reviewed for accuracy, relevance, and alignment with the current syllabus. Spreadsheets have no mechanism to track when each question was last reviewed, flag questions due for review, or prevent the use of stale questions in live exams.
4. No Statistical Analysis
Well-managed question banks use item analysis to identify problematic questions — those that are too easy, too difficult, or ambiguous. Key metrics include discrimination index, difficulty index, and distractor analysis. A spreadsheet cannot perform these calculations automatically across thousands of exam sittings.
5. Security and Access Control
Exam security is a fundamental Part 147 requirement. A spreadsheet on a shared drive is inherently insecure — anyone with access can copy, modify, or extract questions. There is no audit trail of who accessed the bank, and no way to restrict access to specific modules or question subsets.
What a Purpose-Built Question Bank System Should Offer
If spreadsheets are the problem, what does a proper solution look like? Here are the capabilities that a Part 147-compliant question bank management system should provide:
- Structured taxonomy — every question tagged by Part 66 module, sub-topic, knowledge level, question type (MCQ, multi-select, true/false), and difficulty rating
- Version history — full audit trail of every question creation, modification, and retirement
- Review cycle management — configurable review intervals with automatic flagging of questions due for review
- Access control — role-based permissions so only authorised personnel can view, edit, or export questions
- Exam assembly engine — configurable rules for automatically generating balanced exams that cover the required syllabus distribution
- Item analysis — automatic calculation of question performance metrics across all exam sittings
- Integration with student records — exam results flow directly into the student's training record without manual data entry
How AMTOS Handles Question Bank Management
AMTOS was designed from the ground up with a structured question bank at its core. Here's how it addresses each of the spreadsheet failure modes:
- Full Part 66 taxonomy — questions are tagged to all 13 modules with sub-topic and knowledge level metadata. The system enforces complete tagging before a question can be activated.
- Automatic exam assembly — exams are generated based on configurable rules that define the number of questions per module, minimum coverage per sub-topic, and random selection from the eligible pool.
- Secure, role-based access — only authorised examiners can create or modify questions. Students and instructors cannot access the question bank.
- Online delivery — students take exams through a timed, secure interface. Questions are randomised per sitting. Auto-submission on timeout.
- Instant grading and record creation — results are calculated immediately and recorded against the student's file. No manual marking, no transcription errors.
- Re-sit tracking — failed modules are flagged automatically. Re-examination scheduling follows documented procedures.
The result: your entire examination lifecycle — from question creation to result recording — runs through a single, auditable system. No spreadsheets required.
The Bottom Line
Spreadsheets served their purpose when your MTO was small and your question bank was manageable. But as your organisation scales — more students, more modules, more NAA oversight — they become a compliance risk. The question isn't whether to move to a dedicated system, but when.
The sooner you transition, the sooner you eliminate the version control chaos, the security gaps, and the manual effort that spreadsheet-based question banks inevitably create.