Resources / Knowledge continuity plan
How to build a knowledge continuity plan for a fleet shop
A knowledge continuity plan is a short written document that names what your shop knows, who holds it, who backs them up, how and when it gets captured, and where it lives once captured. This page walks through building one in about a month and gives you the template to fill in.
What a knowledge continuity plan is, and what it is not
The name comes from NASA. Its knowledge capture and transfer working group reviewed how the agency handles departures and published its findings in 2021. The top line recommendation was to "standardize processes, templates, and guidance to support knowledge capture for personnel and project transitions" (NASA, Ensuring Knowledge Continuity during Employee Transitions, 2021). A continuity plan is that template, scaled down to a shop with six technicians and one parts person.
It is not a succession plan. A succession plan is about people: who steps into which role, on what timeline. The continuity plan is about knowledge: what has to survive regardless of who is in the role. The two dovetail, and there is a separate page on building a mechanic succession plan. Do the continuity plan first. It tells you what the succession plan has to hand over.
It is also not a binder of procedures. SOPs are one output of the plan, not the plan itself. The plan is the ledger that says which SOPs exist, which are missing, and who is responsible for the missing ones. Which SOPs a fleet shop needs covers the procedures side.
Keep it short. Two pages is plenty for most shops. A plan that takes an afternoon to read will not be read in the week it is needed.
NASA's three phases, translated to a shop
NASA's supervisors' guide to knowledge continuity organizes the work into three phases rather than a numbered checklist: set the culture, keep knowledge current, and maintain knowledge through transitions (NASA, Knowledge Continuity: A Guide for Supervisors, undated). The guide is written for engineers and program managers. The phases carry over to a fleet shop with little translation.
| NASA phase | In a fleet shop | Plan section that covers it |
|---|---|---|
| Set the culture | Make it normal to record a fix, not a favor. Five minutes after a hard repair, by voice, before the next job. The foreman does it too. | Capture schedule |
| Keep knowledge current | A standing cadence for review. Bulletins get filed the week they land. Overrides get re checked when a unit is replaced. | Review cadence |
| Maintain through transitions | On notice, the plan already names what has to be handed over and to whom. The guide's own words: "as soon as you know someone plans to retire or transition out of your organization, sit down with them to come up with a plan." | Holders and backups |
The guide makes two more points that shape the template below. It recommends shadowing as "the best method for transferring knowledge to your new employee or team member" when time allows, and it notes that clips of three to five minutes "can pass information without overwhelming viewers." So the plan budgets for both: a shadowing pairing per holder, and a capture format that is short by design.
The fleet shop knowledge continuity plan template
Copy the six sections into whatever you write documents in. Each row shows the field on the left and what goes in it on the right. Fill in what you know today and leave the rest blank. A blank row is information too: it tells you where the plan is threadbare.
1. Knowledge inventory
2. Holders and backups
3. Capture schedule
4. Collection sources
5. Storage
6. Review cadence
Filling the plan in, one month, no consultants
The plan is built by the foreman or the fleet manager, with about an hour a week from the people who hold the knowledge. Here is a sequence that fits in four weeks.
- Week one: inventory by walking the shop.
Use the six hiding places from tribal knowledge in fleet maintenance. List every knowledge area you can name in an hour. Do not rank yet. Twenty to forty rows is normal.
- Week one, same day: ask the people around the holder.
NASA found it helpful for those doing capture "to talk with others who have worked with the employee to find out what they are most worried about losing." The parts person and the newest tech will name areas the senior himself would not think to mention.
- Week two: name holders and backups.
One name per row in the primary column. Where the backup column says "none yet", that row is your priority list. Pair a shadow to each of those rows before you do anything else.
- Week three: set the capture format and slot.
Default to a voice clip of three to five minutes recorded right after the repair. Written SOPs only for the areas that are procedural and repeatable. Book one weekly slot per holder and hold it.
- Week three, in parallel: run the collection.
Scan the annotated manuals. Export the chat photos. Pull the work order free text. This is clerical work, and it can go to whoever has the time rather than the senior.
- Week four: pick storage and sign the review cadence.
One place, searchable by unit and system, with a supervisor approval step. Then put the quarterly review on a calendar with a named owner. A plan without a date on it is a wish.
Why most continuity plans die by month three
They die because they were built for a departure and the departure happened. The plan did its job once and went in a drawer. NASA's own review found exactly this: capture "is retroactive after identifying the individual who is departing," and the group's recommendation was "a proactive, ongoing process where knowledge capture begins much earlier regardless of an employment status."
Three habits keep the plan current. First, the trigger reviews in section six. A new hire, a replaced unit, a bulletin, a notice: each one reopens the plan for fifteen minutes. Second, the weekly capture slot stays on the calendar after the retirement it was created for. Third, the storage has to be where techs actually look. If captured knowledge sits in a folder nobody opens in the bay, the plan is a record of what was lost slowly instead of quickly.
The interview half of capture has its own page, how to run knowledge capture interviews with fleet veterans, including the questions that get real answers. Use it for the rows in the plan where the format is a voice clip.
Section five of the plan, done for you
Sections one through four of the template are shop work and stay shop work. Section five, storage and retrieval, is what YardWise is for. It holds four levels of knowledge, manufacturer, fleet, engineer, and equipment, and returns one cited answer. A holder records a clip by voice, it gets tagged to the unit and system, and a supervisor approves it before anyone relies on it. That approval step is the plan's "who signs off" row, built in.
Collection sources go in as they are. Scanned margin notes, a phone photo of a binder page, a PDF bulletin. The equipment roster comes in as a CSV. A tech in the bay asks by push to talk voice and gets the answer in under five seconds with the manual page and the holder's name attached. The how it works page shows the full path from clip to answer.
One limit, stated plainly. YardWise does not write the plan or do the interviews. It does not schedule PM or keep your maintenance records. It is the shelf, and the shelf only matters once you have decided what goes on it.
Continuity plan questions, answered short
What is a knowledge continuity plan?
A short written document that names what a shop knows, who holds each area, who backs them up, how and when it is captured, and where it is stored. NASA uses the term for its own knowledge transfer practice. For a fleet shop, two pages covers it.
How is a continuity plan different from a succession plan?
A succession plan is about people: who steps into which role and when. A continuity plan is about knowledge: what has to survive regardless of who holds the role. Build the continuity plan first. It tells the succession plan what to hand over.
How long does it take to build one?
About four weeks of part time effort by a foreman or fleet manager, with an hour a week from the people who hold the knowledge. The inventory takes an hour of walking the shop. The rest is naming backups, picking a capture format, and putting a review date on the calendar.
What format should captured knowledge be in?
Default to voice clips of three to five minutes recorded right after a repair, which is the length NASA's supervisors' guide recommends for passing information without overwhelming viewers. Use written SOPs for procedures that repeat the same way every time.
Who owns the plan?
One named person, usually the foreman or fleet manager, with a quarterly review on the calendar. Trigger reviews happen when someone gives notice, a unit is replaced, a bulletin lands, or a new hire starts.
Does the plan need software?
No. The plan is a document. Storage and retrieval, section five, is where software helps, because captured knowledge has to be findable in the bay to be worth capturing. That is the part YardWise does.
See a continuity plan with the answers already in it
Bring your knowledge inventory, even a rough one. We will show you what the captured entries look like when a tech asks for them by voice in the bay.
Book a demo