Forum Discussion

AnthonySalazar's avatar
AnthonySalazar
Jobber Ambassador
16 days ago

What would you document first if you had to train someone tomorrow?

I’ve been thinking about this a lot lately because my role in the business is starting to change.

There are 2 different parts of the business I’m looking at right now:

  1. The physical labor
  2. The operational work behind the scenes

The physical labor is the part I cannot automate.

At the end of the day, someone still has to show up, walk the yard, find the waste, scoop thoroughly, secure the gate, follow the customer notes, and deliver the actual service.

AI is not coming to scoop the yard for me.

At least I hope we are not there yet. 😂

So that side still has to be trained the old-fashioned way:

  • job flow
  • walking patterns
  • scooping technique
  • equipment handling
  • gate procedures
  • dog safety
  • customer notes
  • completion expectations
  • what to do when something looks off

That part has to be repeatable because customers are not paying for “close enough.”

They are paying for a consistent result.

The operations side is where things are getting interesting for me.

A lot of tasks I thought might eventually require an office person are starting to become easier to automate, delegate, or systemize with tools like Claude and other software.

Things like:

  • drafting follow-up messages
  • organizing processes
  • helping with SOPs
  • creating scripts
  • reviewing notes
  • cleaning up admin workflows
  • building internal checklists
  • helping think through customer communication

That has made me rethink what actually needs a person versus what needs a better process.

There are still plenty of tasks that require judgment.

But I’m realizing some of the “office work” I thought I needed to hire for may actually be a process problem first.

So if I had to train someone tomorrow, I’d probably separate documentation into 2 buckets:

Field work:
What does the customer physically receive?

Operations:
What has to happen before and after the job so the customer experience feels organized?

Both matter.

A great technician with messy operations still creates customer problems.

Clean admin with poor field work still loses trust.

If you had to train someone tomorrow, what would you document first: the physical labor, the office/admin side, or the customer communication process?

13 Replies

  • For me, it would be the customer journey. What happens when someone calls? How do we document the lead? When do we follow up? How do we create the quote? What happens after the quote is sent? What happens after they become a customer?

    I found that documenting the operational side first had the biggest impact because that's where a lot of knowledge was living in my head. Once we documented those processes, it became much easier to hand off pieces of the business. Our virtual assistant wasn't asking me what to do next because there was already a process for it.

    The field work is obviously important too, but if I had to start somewhere tomorrow, I'd start with the workflows that happen before and after the job.

    • AnthonySalazar's avatar
      AnthonySalazar
      Jobber Ambassador

      Something that really helped me on the customer journey/operations side was creating Loom videos for every step in the journey. So when a new quote is generated, I create one quick loom video on exactly how we process that quote, and what gets sent to the client and all of our Loom and associated SOPs live in a Trello board that I've handed off to my VA for training.

  • TurfT's avatar
    TurfT
    Contributor 4

    For me it was the field work first — and the easiest way I found to document it was through a Jobber job form attached to every visit. It's basically a custom job completion checklist your create to make sure things aren't missed.

    You build it once, it shows up on every job. Mine includes a weather screenshot upload, a dropdown of every chemical I use with concentration and rate pre-filled, a fertilizer checkbox, completion photos of the front and back of the property, and photos of any existing damage. If a client ever claims I killed their plants, I have photos showing it was already like that when I arrived.

    Clients can see everything through the Jobber client hub — what was applied, photos, all of it. They get notified before the treatment and when it's complete. I don't send manual updates anymore, unless it's something important.

    Doesn't take long to set up and it runs on every job automatically. Start there. 

  • Great question Anthony. Here's a bit more of a macro perspective.

    Field work and operations are actually both sitting inside the same workflow, Lead to Cash. Everything you listed, the yard walk, the gate check, the admin, the customer communication, that's all money coming in.

    The workflow you didn't mention here is Procure to Pay. Equipment, supplies, fuel, subcontractors. Everything that has to happen before you can even deliver the service.

    Most home service operators run that entire side of the business on memory and a credit card statement and then wonder why margin is hard to predict.

    If I had to train someone tomorrow I'd start by mapping both flows first. Lead to Cash and Procure to Pay. Once you have those two on paper everything else becomes clear and you can break those macro processes down into micro processes. What to document, what to delegate, and eventually what to automate.

    • AnthonySalazar's avatar
      AnthonySalazar
      Jobber Ambassador

      This is a really solid way to look at it.

      I hadn’t thought about it in those exact terms, but Lead to Cash and Procure to Pay makes a lot of sense. A lot of us document the customer-facing side first because that’s where the pain is loudest.

      Lead comes in.
      Quote gets sent.
      Customer gets scheduled.
      Technician does the work.
      Customer gets updated.
      Invoice gets paid.

      That side is easier to see because it directly affects the customer experience.

      But the Procure to Pay side can quietly create margin issues in the background.

      For us, that would be things like:

      • bags
      • deodorizer/sanitizer
      • fuel
      • vehicle maintenance
      • tools
      • uniforms
      • gloves
      • dump fees
      • replacement equipment
      • software

       

      And you’re right, a lot of that can live in the owner’s head for too long.

      I’ve definitely had times where I knew what we were spending in general, but I didn’t have the process as clearly documented as the field work or customer communication side.

      That becomes a problem when you’re trying to understand the true cost of a visit.

      The route can look good.
      The customer can be happy.
      The tech can do the job correctly.

      Then you realize margin is getting eaten up by supplies, fuel, wasted trips, broken equipment, or purchasing decisions that were never standardized.

      I like the idea of mapping both flows first, then breaking them down.

      For my business, I’d probably look at it like this:

      Lead to Cash:

      • lead intake
      • quote
      • follow-up
      • scheduling
      • route assignment
      • service checklist
      • customer communication
      • completion notes
      • billing
      • review request
      • retention follow-up

       

      Procure to Pay:

      • what supplies are needed
      • who orders them
      • when they get ordered
      • where they’re stored
      • how inventory is tracked
      • how fuel and dump fees are handled
      • what equipment gets replaced and when
      • what costs need to be tied back to the actual service

       

      That second side is probably where a lot of home service owners are losing money without realizing it.

      Appreciate you laying it out this way.

      It’s a good reminder that documentation isn’t just about training employees to do the work. It’s also about understanding what the work actually costs to deliver.

      • Randy_Warner's avatar
        Randy_Warner
        Contributor 4

        Spot on  AnthonySalazar​! Now that you have each of those steps laid out I would "zoom in" to each one and walk through exactly what happens at each step. Who are the parties involved, what information is needed, what are the steps/dependencies for each step, etc. and then document that micro process.

        Personally I use LucidChart because I like a visual layout and it's easy to update when things change. From there, I create/revise a Google Doc for the process document itself based on a standard template. At a certain point you can look at things like Trainual or Whale for process document and sharing amongst the team.

  • MTLcontractors's avatar
    MTLcontractors
    Jobber Ambassador

    I’d probably document the field work first, but only because that’s where the customer experience can fall apart the fastest.

    For us in renovations, the first things worth documenting are usually the repeatable site standards: how the site gets protected, how photos are taken, what gets checked before closing walls, how deficiencies are logged, how materials are received, and what needs to be communicated before the end of the day.

    The admin side matters a ton too, but if the field process is inconsistent, the office ends up constantly reacting to problems after the fact.

    I like your split between physical work and operations though. In construction, I’d almost add a third bucket: handoff points. The moments where information moves from sales to production, PM to crew, crew to client, or trade to trade. A lot of mistakes happen there. Learned that the hard way a long time ago.

    • Homeownership's avatar
      Homeownership
      Contributor 4

      Processes create consistency. If the business depends on one person remembering everything, that's a risk.

    • AnthonySalazar's avatar
      AnthonySalazar
      Jobber Ambassador

      I think focusing on field work first is the right move! The less call backs and complaints you have because of breakdown in processes out in the field will result in less admin time following up with the client, less angry calls your office staff needs to deal with, and less awkward conversations with your techs on how balls were dropped. 

      • MTLcontractors's avatar
        MTLcontractors
        Jobber Ambassador

        Beautifully said. Admin time is a huge drain that's better spent as a faucet to processes.

  • Break up the training into tasks and days.  We have a 5 day training plan and each day we introduce something new, while repeating the day before. 

    • AnthonySalazar's avatar
      AnthonySalazar
      Jobber Ambassador

      How did you figure out which building blocks to apply on each day? That's a very similar structure to what we do - we have our techs follow along the jobber app, send on the way messages and review instructions, and teach them our SOPs for walking the yards and scooping. And each day we add a little more that builds on what they learned from the previous day.

  • roselvaggio's avatar
    roselvaggio
    Jobber Ambassador

    Revenue generates from the physical labor, so my efforts naturally went there first. Everything was always (and still is) subject to revision because the type of company we were to get to here isn’t the type of company that gets to the next level. Hope this helps!