Log in GO PRO NOW
GO PRO NOW
Your workflow could help someone. Share it!

Guides ChatGPT

Cut Onboarding Time in Half With Loom and ChatGPT

In this guide, you will learn how to turn a short Loom walkthrough into a clear onboarding SOP with ChatGPT.

beginner 5 steps

Introduction

In this guide, you will learn how to turn a short Loom walkthrough into a clear onboarding SOP with ChatGPT. You will end with a Markdown SOP you can paste into Google Docs for the next person to use.

Step-by-step 5 steps

Instructions

  1. Step 1 of 5

    Record a Task Someone Else Needs to Repeat

    Choose a task you do often and record yourself doing it in Loom. Good starting points include filling out a timesheet, writing a report, or sending an email to a specific client. Explain the clicks, the decisions you make along the way, any exception that should stop the process, and what a finished result looks like.

    In the video, the task is logging weekly hours in Google Sheets. The walkthrough shows the hours entered, the weekly total, the READY TO FILE status, and the next action: make a copy and save it in the completed-timesheets folder. Those details turn a screen recording into something another person can actually follow.

    Source timesheet workflow
    Source timesheet workflow
  2. Step 2 of 5

    Clean Up the Transcript

    When you finish recording, use Loom's transcript editor to remove mistakes or long silences. You do not need a perfect script. You do need a transcript that reflects the useful path through the task.

    Pro tip: Clean up mistakes and long pauses before you hand the transcript to ChatGPT. A cleaner source produces a cleaner SOP.
  3. Step 3 of 5

    Copy the Transcript Into ChatGPT

    Copy the cleaned Loom transcript into ChatGPT. Add the links, screenshots, or short visual notes a new teammate needs, especially when a value, file name, destination folder, or status is only visible on screen.

    Then tell it to write the SOP in Markdown. Keep the request focused on the process you recorded instead of asking it to fill in missing details. Here is a compact starting prompt:

    Prompt 
    Use this Loom transcript and the linked resources to write an onboarding SOP in Markdown. Keep the process in the same order, and do not add details that are not in the source.

[PASTE TRANSCRIPT]

    ChatGPT gives you a first written version to work from. Treat it as a draft: read it against the recording and correct anything that no longer matches the task.

  4. Step 4 of 5

    Give the SOP a Useful Format

    If the first version is not organized this way, ask ChatGPT to reshape it into four parts: purpose, links to resources, steps, and then a checklist. That gives the reader context before they start, the files they need while they work, and a simple way to check the result at the end.

    In the timesheet example, the resource section points to the template and completed-timesheets folder. The steps explain how to log the hours and make the copy. The checklist confirms the date, hours, total, filing status, and copied Sheet all carried over.

    Reviewed SOP purpose
    Reviewed SOP purpose

    Make the exception plain rather than hiding it in a long paragraph. For example, the demo SOP says to stop and message Ops if the weekly total is over 40 hours or the status is not READY TO FILE. Your own SOP should name the point where a teammate should pause and ask for help.

  5. Step 5 of 5

    Paste the Final SOP Into a Google Doc

    Once the SOP reads like the process you recorded, paste the final version into a Google Doc. Use clear headings so the purpose, resource links, steps, and checklist are easy to scan while someone works through the task.

    Pro tip: If you ask it to build the SOP in Notion, it can embed the Loom video so it is playable right on the page.

    The Google Doc is the written reference. The Loom remains useful when someone needs to see the original clicks or hear the explanation behind a decision.

You're done

That's the whole workflow

Mark it complete to save your progress. Background and answers to common questions follow below.

Keep going

Keep learning with Rundown Pro

A guide shows you one workflow. Pro opens the full course library, so you can learn the whole system behind it.

  • Every on-demand course
  • Certifications on completion
  • Group office hours and member perks

$29/mo, cancel anytime

Overview Back to the steps

Background and context

Who This Is Useful For

  • Operations leads who need a dependable way to document recurring team processes before a new hire needs them.
  • Consultants and client-service teams who want to turn a recorded handoff into a clear procedure for a specific client.
  • Anyone who repeats a task such as submitting timesheets, writing reports, or sending client emails and wants a reusable explanation of it.

What You Will Build

You will turn one short screen recording into an SOP a teammate can follow: a purpose, links to the resources they need, the steps in order, and a checklist that shows when the work is done. The weekly-timesheet example below is the model; use the same process for your own repeatable work.

Private SOP handoff
Private SOP handoff

What You Need To Get Started

  • A Loom walkthrough of one repeatable task.
  • The Loom transcript, plus links or screenshots for details that only appear on screen.
  • ChatGPT.
  • Google Docs for the final SOP.

Going Further

This is really important and helps you stay organized: build a Google Sheet index for finished SOPs by team or process, so teammates can find the right handoff quickly. Add one row per SOP with its title, owner, team, process, last-reviewed date, and a link to the Google Doc or Notion page.

Start with the tasks people ask about most often. Then update the recording and the written SOP together whenever the process changes. The goal is not to document everything at once; it is to make the next repeated handoff easier to find and follow.