An aviation edit SCORM file job is a change to a published aviation course package, such as a revised regulation reference, a new logo or a corrected figure, made without the authoring project the course was built from. Small text and image edits are often possible inside the package. The harder part in aviation is controlling the change and keeping each learner’s record meaningful.
Training providers meet this problem when a client hands over a recurrent course built years ago by a vendor that no longer exists, after the manual changed and nobody kept the authoring file. Our guide to editing a SCORM file without the source files covers the mechanics. This post adds the aviation layer: who must agree to the change, what to log, and how to protect completion records.
We did not test any LMS behavior described here. It comes from each vendor’s published documentation. This is not regulatory advice. Your approval, your quality system and your authority decide what is allowed.
Key takeaways
- Treat every edit to an aviation SCORM package as a controlled change with an owner, a reason, an approver and an effective date.
- Export completion and in-progress reports before you upload an edited package, because LMS behavior differs and some reports do not show which package version a learner used.
- Keep the manifest identifier unchanged for editorial fixes. Change it only for scoring or structure changes, after checking your LMS documentation.
- Patch text, images and logos. Rebuild when the edit touches structure, scoring or interactions.
What does an aviation edit SCORM file job involve?
An aviation edit SCORM file job means opening a compiled SCORM package, which is a ZIP of web files plus an imsmanifest.xml file, and changing content inside it. Typical triggers are a revised regulation citation, a new organization name or logo, and an outdated manual reference. The edit is technical, but the consequences for records and approval are aviation-specific.
Without the source project you edit the output, not the design. Authoring community threads say a published course is a publication, and a clean, updatable version needs the original file. Text, images, audio, video and links can often be changed in the package. An August 2026 article from Elephant, an import-based alternative vendor, warns that tracking variables, quiz passing rules and JavaScript interactions can break if edited without understanding the logic.
Anything that changes scoring, structure or tracking is closer to a rebuild, and our SCORM rescue checklist for old courses shows how to score that decision.
Which aviation edit SCORM file changes need approval before you ship?
The authority that approved the training program, not the person editing the file, decides which course changes need approval. For a US repair station, 14 CFR 145.163(d) says it “must submit revisions to its training program” to its responsible Flight Standards office. Whether a given course edit counts as a revision is a question for that office.
Cornell Law School’s 14 CFR 145.163 page (read October 2026) adds in paragraph (a) that a repair station “must have and use an employee training program approved by the FAA that consists of initial and recurrent training.” Paragraph (c) says training records “must be retained for a minimum of 2 years.” In Europe, EASA’s FAQ on Part-145 training requirements, last updated 2 February 2021, quotes point 145.A.35(d): staff “receive sufficient continuation training in each two-year period to ensure that such staff have up-to-date knowledge.”
These are examples, so check with your own authority. Nothing here means a course or tool is approved by a regulator. The table is our own triage of common legacy edits, rated by judgment rather than testing.
| Edit trigger | Where it usually lives | Who to ask before release | Record impact |
|---|---|---|---|
| Typo or wording fix, meaning unchanged | Screen text in HTML or JavaScript files | Course owner, under your document control rules | Low. Keep the identifier. |
| Regulation or manual citation updated | Screens, quiz feedback, narration, captions | Quality or training manager; your authority if your procedures require it | Medium. Earlier completers saw the old wording, so log the revision. |
| Logo, organization name or approval number | Images, header text, certificate screen | Quality manager. Copy numbers from approved documents. | Low, unless the completion screen changes what it states. |
| Pass mark, quiz question or screen count changed | Manifest, course code, question data | Training manager, and likely your authority if the assessment is part of the approved program | High. Consider a new identifier, because bookmarks may no longer match. |
| Recurrent interval text on screen | Screen text | Training manager | Medium. The due date rule lives in the LMS, so text and LMS can disagree. |
Pro tip: Ask the Approval Question Once, in Writing. Before opening the file, send your quality manager a one-page change request listing the screens affected and the reason. The reply tells you whether this is a quick fix or a revision, and gives you the approver and effective date for the log.
How do you edit the package without breaking learner records?
Protect learner records by freezing them first, then keeping the manifest identifier unchanged for editorial fixes. Export completion and in-progress reports before uploading the edited package. LMS platforms differ on identifiers and in-progress learners, so read your vendor’s documentation and rehearse with two test learners before the real upload.
The vendor pages we read differ in detail, which is why rehearsal matters. As of October 2026:
- Totara’s update a SCORM activity page (August 2024) says completion and progress are kept only if the new manifest has the same item identifier as the current one.
- Dual Code’s SCORM identifier documentation (June 2026) says a changed identifier leaves records in the database but unlinks old attempts from standard reports.
- The Go1 article on updating a SCORM file without disrupting learners (July 2026) says replacing the ZIP does not overwrite completion records, and learners already in progress stay on the version they started.
Follow this sequence for any edited package:
- Export completion and in-progress reports, and file them with the revision record.
- Download the current package as a backup, and note its manifest identifier.
- Edit a copy, then compare the identifier before and after.
- Upload to a staging course and test with two learners: one fresh, one mid-course on the old revision.
- Release only after the approver has signed and the effective date is set.
Avoid deleting enrollments to force everyone onto the new version. Go1 describes that as irreversible, with saved progress lost and results removed from standard reporting.
How do you edit text, images and logos in a legacy package?
To edit a legacy package, copy the original ZIP, unzip the copy into a clean folder, find the text or image, change it minimally, confirm the manifest still parses, and re-zip so imsmanifest.xml sits at the ZIP root. Keep the untouched original archived.
Aviation courses add traps that generic guides skip:
- Old references hide in many places. Search screens, quiz feedback, audio scripts, captions and downloadable job aids.
- Diagrams carry text. A regulation number baked into an image will not appear in a text search, so replace the image.
- The course title is not the identifier. The manifest title is a separate field, so you can retitle a course for a new revision without touching the identifier.
What should the revision record for an edited aviation course contain?
The revision record for an edited aviation course should capture what changed, why, who approved it, when it took effect, which package and identifier went live, and how learners were treated. Go1’s help center says its standard reports do not show which ZIP version a learner used and advises keeping your own release log. Other LMSs may differ.
Use this template, one entry per edit, kept with the course file:
| Field | What to record |
|---|---|
| Course ID and revision | Your course number and revision number, written the same way everywhere |
| Trigger | The document, bulletin or event that prompted the change, with its date |
| Change summary | Screens, quiz items and media touched, old wording against new |
| Approver and date | Name, role, sign-off date and any authority correspondence reference |
| Effective date | The date learners first see the new revision |
| Package and identifier | File name, checksum if you use one, manifest identifier before and after |
| Records action | Names of exported reports, who stays on the old revision, who retakes |
| Tested by | Tester, LMS and browser, and the result of each check |
Pro tip: Put the Revision on Screen One. Show the revision number and effective date on the first screen and in the LMS course title. Where reports do not show the package version, a title or screen that does gives you a second trail. Confirm what your LMS displays in transcripts before relying on it.
How do you test an edited aviation course before learners see it?
Test an edited aviation course in a staging area of the LMS your clients use, with two test learners, from launch to completion. Check every edited screen, both sides of the pass mark, resume from a bookmark and the completion record the LMS stores, then file that record with the revision log. A successful upload proves little.
Our SCORM package QA checklist for client LMSs has the general list. For aviation edits, add two checks:
- A second person compares each changed screen against the document that triggered the change.
- The mid-course test learner confirms which revision your LMS serves to learners already in progress.
When should you rebuild an aviation course instead of editing it?
Rebuild an aviation course when the change touches structure, scoring or interactions, or when regulation changes keep arriving. The Elephant article says patching reaches its limits for structural rework and new chapters, and a practitioner thread on the Articulate community reports progress resets when slide counts change.
If you edit the same course every quarter, each patch adds risk, and a rebuilt course with a source file is easier to keep current. Our post on course version control when regulations change covers the process, and aviation course version control applies it to aviation.
Is there an aviation SCORM editor that works without source files?
SimpliAuthor’s paid Visual SCORM Editor is described on its product page as editing compiled SCORM without the source files. We have not tested it. Disclosure: SimpliAuthor is a SimpliTrain product from the same company that publishes this site, and its page does not say which elements the editor can change, which SCORM versions it supports or what it costs.
Whatever tool you consider, ask these questions before trusting it with an aviation course:
- Can it edit quiz questions and feedback, not just screen text?
- Does it change the pass mark in both the manifest and the course code?
- Does it preserve the manifest identifier, or warn you before it changes?
- Does it leave the original untouched and produce a change list for your revision record?
Trial any editor on one real legacy course. The SimpliAuthor product page is the place to check current plan details.
What should you do next?
Pick one legacy aviation course and run it through the triage table. List the edits waiting, mark which need approval, and ask your quality manager the approval question in writing. Then freeze the reports, edit a copy, test in staging and complete the revision record before release.
If your larger problem is tracking revisions and recurrent records across many courses, you can request a SimpliTrain demo and ask how course version changes and completion records are handled. SimpliTrain and SimpliAuthor come from the same company that publishes this site, so judge them against the questions above.
Frequently asked questions
Can you edit an aviation SCORM file without the source files?
Often yes for text, images and logos, because a SCORM package is a ZIP of web files you can unzip, change and re-zip. Scoring, structure and interactive logic are riskier. In aviation, confirm with your quality system whether the change needs approval before release, and keep an untouched copy of the original package.
Will learners lose their records when I upload an edited SCORM package?
It depends on your LMS. Totara’s documentation says progress and completion are kept only when the manifest item identifier matches. Go1 says replacing the ZIP does not overwrite existing completion records. Export completion and in-progress reports first, then rehearse with test learners.
Who approves a change to an aviation training course?
The authority or approval holder that approved the training program decides, and rules differ by country and organization type. For a US repair station, 14 CFR 145.163(d) routes training program revisions to its responsible Flight Standards office. Ask your quality manager and authority, because this site cannot give regulatory advice.
What should I record when I edit an aviation course?
Record the course ID and revision, trigger, change summary, approver and date, effective date, package file name and manifest identifier, reports exported, and test results. Also show the revision on the first screen, since some LMS reports do not show which package version a learner took.
Should I edit an old aviation SCORM course or rebuild it?
Edit when the change is text, an image or a logo. Rebuild when structure, scoring or interactions change, or when edits keep arriving every few months. SimpliAuthor lists a paid Visual SCORM Editor for editing without source files, which we have not tested, so trial it on one real course first.



