ISP Field Tech Onboarding Guide: How to Capture 7 Years of Knowledge in 30 Minutes

The short version: When a fiber ISP's best field tech gave notice after seven years, the operations team used one AI prompt and a 30-minute conversation to turn his institutional knowledge into a complete new hire onboarding guide. Here is exactly how to do the same thing at your ISP, before anyone gives notice.An ISP’s best field technician, Marcus, put in his two weeks on a Tuesday morning.

By Wednesday, three people had already mentioned his name in the same sentence as "what do we do about."

He had been with that ISP for seven years. He knew the fiber routes on the east side better than the GIS system did. He knew which customers were going to argue about ONT placement before he pulled into the driveway. He knew about the splice on County Road 4 that looked fine but needed checking every winter. He knew the 811 landscaping problem in one particular subdivision and how to work around it. He knew things he did not even know he knew until someone sat down and asked him.

That is the part nobody talks about when a key employee leaves. Not the job posting, not the interviews, not the offer letter. It is the seven years of field judgment that lived inside someone's head and is now scheduled to walk out the door in fourteen days.

For most ISPs at the 20,000-subscriber level, that institutional knowledge does not exist anywhere else. It is not in a manual. It is not in the ticketing system. It is not even in someone else's memory in a form that could be written down and handed to the next person. It just lives in the person who has been there longest.

They had three new hires starting in thirty days. They were in the middle of a BEAD build. There was no shadow period. There was no time for a new tech to absorb what took Marcus seven years to figure out.

So they tried something that took an afternoon.

The 30-Minute Brain Dump: How One Field Tech Session Becomes a Full-Onboarding Document

They sat Marcus down and asked him to talk. Not to write anything. Not to open a document or fill out a template. Just talk. And they recorded it via Google Meet so they had the transcript.

What do you check before you leave the shop? What do new guys always get wrong on their first solo install? What is the thing that took you three years to figure out that nobody told you? Walk me through a bad callback. What are the first three things you check?

The whole session was about 800 words of real, practical, slightly messy knowledge. ONT placement rules. Why Marcus buries 18 inches instead of the code minimum. What to do when a customer insists the equipment goes in the garage. The two most common callback patterns he had seen. The end-of-day truck check he does without thinking about it.

Then they pasted that transcript into Claude and ran one prompt.

The prompt was a single sentence:

"Turn this into a field technician onboarding guide for a new hire at a 20,000-subscriber fiber ISP. Include a step-by-step install process, common troubleshooting scenarios, and tips from an experienced tech. Write it clearly enough that someone on their first solo install could follow it."

What came back was a complete onboarding guide. Numbered steps. A materials checklist. A troubleshooting section organized by the most common callback reasons. A tips section that still sounded like Marcus because it was Marcus's words, just organized.

They reviewed it, corrected two things he had forgotten to mention, added their specific truck check protocol and photo documentation requirement. Done. Seven years of institutional knowledge, captured and structured in an afternoon.

I made a short video walking through this process from the brain dump to the final document. You can watch it below.

How to Create an ISP Field Tech Onboarding Guide with AI: Step-by-Step

You do not need to wait until someone gives notice. The best time to do this is before there is any urgency at all. Here is exactly how:

Step 1: Schedule the conversation and tell them what it is for.

Thirty minutes. No prep required on their end. You are going to ask them questions and take notes, or record with their permission. Frame it simply: "I want to make sure we have what you know written down so we can teach it to the next person."

Most experienced field techs are genuinely glad to do this. They know things that matter and there is real satisfaction in having that acknowledged.

Step 2: Ask questions that unlock the earned knowledge, not the official version.

The official version is in the manual. What you want is the version that took years to develop. Use questions like:

• What do you check before you leave the shop that is not on any checklist?

• Walk me through a typical install from truck to job-complete. Where can things go sideways?

• What do new hires always get wrong in their first three months?

• What took you two or three years to figure out that nobody told you directly?

• What is the most common callback reason at your ISP, and what do you check first?

• What do you know about our service area, our customers, or our infrastructure that a new person would not?

Do not interrupt. Let them go. Messy and rambling is fine. You are not writing the guide in this room.

Step 3: Get the conversation into text.

Record the session and use a transcription tool like Otter.ai, Google Docs voice typing, or the voice transcription feature built into ChatGPT, Claude, or Gemini. Or take rough notes during the conversation and clean them up immediately after.

The text does not need to be polished. Rough notes work fine. Incomplete sentences work fine. The AI is going to organize it.

Step 4: Write your prompt.

Paste this exactly, then adjust the specifics to match your operation:

"Turn this into a field technician onboarding guide for a new hire at a [subscriber count] [fiber/WISP/hybrid] ISP. Include a step-by-step install process, common troubleshooting scenarios organized by frequency, and tips from an experienced tech. Write it clearly enough that someone on their first solo install could follow it."

The more specific you make the prompt, the more useful the output. If you have a particular focus area, name it: customer premises equipment, ONT placement, buried plant, aerial drops, whatever fits your infrastructure.

Step 5: Paste the transcript and run it.

This works in Claude, ChatGPT, or Gemini. Open a new conversation, paste the prompt, paste the transcript below it, and let it run. The same workflow is tool-agnostic. Use whatever your team already has access to.

What comes back will be a structured first draft. Numbered steps, organized sections, and the specific knowledge from your tech preserved because it came from their words.

Step 6: Review with someone who knows the role.

This is the step that makes the document actually yours. Read it with another experienced tech or your field ops supervisor. Ask: what is missing? What did they forget to mention? What is specific to our systems and protocols that is not in here?

Common additions: your specific ticketing system steps, photo documentation requirements, internal escalation contacts, equipment model-specific notes, and company policies that are second nature to a ten-year employee but invisible to a new hire.

Plan on thirty minutes of review and editing. The 800-word brain dump becomes a working onboarding document in about an hour total.

Step 7: Format it and put it somewhere findable.

Export it as a PDF. Put it in your onboarding folder. Add it to your field tech training materials. Set a reminder in six months to review it and update anything that has changed, especially after infrastructure upgrades or service area changes.

That is it. One 30-minute conversation, one prompt, one editing session.

Applying This to Every ISP Role That Carries Institutional Knowledge

The same process works for any role where critical knowledge lives in one person's head.

Your NOC engineer who has been building out your network for six years. Your billing specialist who has been with the company since the WISP days and knows every exception in your system. Your GM who carries the franchise relationship history in their head.

Think about your ISP right now. Who is the person where, if they left tomorrow, the first three questions from your team would be "what do we do about everything they know?"

That is who you do this with first. And you do not wait for the resignation letter.

The ISP Back-Office AI Playbook has this workflow and seven others, all written specifically for broadband operators. Free download, no form, HERE.