Problem guide
New hires take months to learn the process
New hires take months because the real process is not in the software or the binder; it lives in a few experienced people and the shortcuts they know. The software teaches too, by what it lets people skip. Field apps differ on what required means: Housecall Pro will not finish a job until required checklist items are done, while ServiceTitan lets a technician pick Fill out later on a required form unless the office sets it to must complete. Map the real workflow, then make the tools hold it.

How it actually happens
Take a new service technician as an example. He has years in the trade and passes the ride-along week without trouble. The work itself is not what slows him down. What slows him down is everything around it that nobody wrote down.
On his first solo day he closes three jobs. The app asked for a maintenance form on one of them, and he tapped the option to fill it out later, because the customer was waiting and nobody told him the form feeds the service agreement report. On another, he found a second failed part, but his role in the app could not add a line item, so he called the office. The dispatcher added it. The third job went fine.
A week later the service manager notices the blank forms, and billing notices the invoice the dispatcher edited went out with the wrong labor rate. Neither of them tells the new technician directly. The service manager mentions it to his mentor, who mentions it at lunch, with half the detail. Each correction reaches him late and secondhand, if at all.
The office has the same problem in a different shape. A new billing coordinator sits beside the person who has done the job for years. She learns that one customer needs a purchase order number on every invoice, another wants copies sent to a second address, and a property manager's portal rejects anything not split by building. Her mentor explains each rule when it comes up, which means only when it comes up. Two months in she is on her own, and an invoice for a large account bounces back because nobody mentioned that customer's portal.
Every kind of business has its version. A new associate in a third-party warehouse packs a client's order the standard way and the client charges back for the wrong label. A new biller at a clinic sends a claim without the referral one payer always wants. A new line cook plates a dish the way the last restaurant did.
On the construction side, a new project manager discovers that he cannot create the cost code he needs in Procore. It has to be added in Sage and approved by accounting before it can be used, and until then the foreman's hours sit on a general code. Nobody told him, because the people who know have not thought about it in years.
In every version, the new hire is not slow. The process has dozens of small rules, most of them exceptions, and the only place they are stored is in the people who have been there longest. Every one of those people is busy, so the rules come out one at a time, usually right after the mistake they would have prevented.
The software is part of the curriculum
Each system enforces different things. In Housecall Pro a required checklist item blocks the job from finishing. In Jobber it prompts and can be skipped. In ServiceTitan a required form can be filled out later unless the office changes its trigger. A new hire learns your process partly from what the software lets them skip, so the setup is teaching whether you meant it to or not.
Signs you have this problem
- New hires keep interrupting the same one or two veterans with the same questions
- Training is mostly shadowing, and every mentor teaches it a little differently
- A new person's work closes with forms left to fill out later that never get filled
- Mistakes by new people surface weeks later, in billing or with the customer
- Experienced staff say it is faster to just do it themselves
What usually causes it
- Most of the real work is handling odd cases, and the rules for those live only in memoryThe exception swamp
- Knowledge passes from person to person, and details drop out at every handoffThe handoff gap
- The process includes retyping between systems, with unwritten tricks for getting it to come out rightThe re-entry trap
Find your cause
Ask these in order. The first yes is usually where yours starts.
- Do new hires ask the same few people the same questions for months?If yes: the process is not written anywhere a new person can find it. Start the question log with the next hire.
- Does a new person's work close with forms or checklist items still blank?If yes: your software is reminding, not enforcing. Test which required items truly block the close and change the ones that matter.
- Do new people's mistakes show up weeks later, in billing or a customer complaint?If yes: nobody reviews their early work while it is fresh. Review the first ten pieces of work within days.
- Do new hires send exceptions to someone senior because their role cannot edit the record?If yes: permissions were left at the default. Set the new-hire role on purpose.
- Does every mentor teach a different way?If yes: there is no agreed version of the workflow. Map one with the best person and teach from that.
How it breaks in each industry
- HVAC and refrigeration service
- A new technician who is not yet EPA certified may not open a refrigerant circuit unless he is a registered apprentice working under close and continual supervision of a certified technician, and apprentice status lasts two years. Part of the ride-along period is a legal requirement, not just training.
- Office and billing staff in any business
- The billing coordinator learns customer by customer: who needs a PO number on the invoice, who wants it sent to a second address, whose portal rejects anything not split by location. None of it is in the accounting system, so it arrives one rejected invoice at a time.
- Logistics and third-party warehousing
- Each client has its own rules for receiving, packing, labeling and shipping. A new warehouse associate learns them by working beside someone who knows them, and a missed client rule surfaces as a chargeback or a client complaint after the shipment has left.
- Healthcare practices and clinics
- Front desk and billing staff learn the payer rules one denial at a time: which plans need a referral, which procedures need prior authorization, which codes a given payer rejects. The rules sit with the longest-serving biller.
Where it breaks between systems
- ServiceTitan required forms
- ServiceTitan documents the problem directly: technicians can select Fill out later on required forms and still close jobs. A form blocks closeout only when the office sets its trigger to Must complete the form at the time of trigger.[1]
- ServiceTitan Field Mobile App closeout
- A job is blocked from completion by required forms, required signatures and required equipment details. The same page tells technicians that their business may require additional steps and to check with their field manager, so the shop's own rules live with a person.[2]
- ServiceTitan technician forms
- For forms triggered by the technician rather than the job, marking a form Required reminds the technician to complete it but does not affect the job workflow.[3]
- Jobber checklists
- Jobber's help center describes required checklist questions as a prompt: the team member is asked to go back and finish, but can still complete the visit with the checklist unfinished, and the office is notified in the activity feed afterward.[4]
- Housecall Pro checklists
- Checklist items marked required, shown with a red asterisk, must be completed before the job or estimate can be marked finished. Here required means blocked, which is not what it means in Jobber or by default in ServiceTitan.[5]
- Housecall Pro field permissions
- Without the Add/edit jobs permission, a technician's jobs and line items are read-only, and access to account settings including price list items is off by default for field techs. A new hire on a default role cannot add the extra part he found on site.[6]
- Procore and Sage 300 CRE (cost codes)
- When someone adds new project cost codes to the Sage 300 CRE standard list, the change goes to the ERP Integrations tool for an Accounting Approver to review, and project cost codes have to be updated before any data can export.[7]
- Procore ERP cost types
- Procore's default cost types are Equipment, Labor, Materials, Other, Owner Cost, Commitments and Professional Services, and Procore notes that not all integrations support the cost type concept. A new hire learns two vocabularies: cost types in Procore and categories on the Sage side.[8]
- Procore and Sage 300 CRE (budget lines)
- If the setting to add new cost codes to budgets automatically is off, a cost code and cost type combination missing from the Procore budget has to be added by hand before its costs display. A new project manager sees costs in Sage that are missing in Procore and does not know why.[9]
By the numbers
| Figure | What it measures |
|---|---|
| 1.8%[10] | Construction quits rate for August 2026 (preliminary, seasonally adjusted): the share of construction workers who quit in that month. The rate was also 1.8% in July 2026, December 2025 and August 2025. Bureau of Labor Statistics, Job Openings and Labor Turnover Survey. |
| 4.0%[11] | Annual average of the monthly total separations rate in construction, not seasonally adjusted, in both 2024 and 2025 (quits, layoffs and other separations). Each departure is a seat a new hire has to learn. BLS JOLTS, Table 20. |
Rules that apply
- 40 CFR 82.161(a)(1) and (a)(2), with the apprentice definition in 82.152[12]
- Anyone who could reasonably be expected to open a refrigerant circuit must pass an EPA-approved certification exam. Apprentices are exempt only while closely and continually supervised by a certified technician, and an apprentice must be registered with the Department of Labor's Office of Apprenticeship or a recognized state agency, for no more than two years from first registering.
- 29 CFR 1926.21(b)(2), construction safety training[14]
- The employer must instruct each employee in recognizing and avoiding unsafe conditions and in the regulations that apply to the work environment. In construction this is a duty owed to every new hire, whatever the onboarding plan says.
- 29 CFR 5.5(a)(4)(i)(A) and (a)(3)(i)(D), apprentices on Davis-Bacon work[15]
- Apprentices may be paid below the predetermined rate only when individually registered in a program registered with the Department of Labor or a recognized state agency, and contractors must keep written evidence of the program and apprentice registrations, ratios and wage rates. Applies only to covered federal and related-act contracts.
Measure it in your own shop
From: Start dates for your last few hires in each role, and their first 60 days of jobs, orders, invoices or entries, with any corrections, returned invoices, callbacks or customer complaints tied to them.
- For each recent hire, list the work they completed in their first 60 days, week by week.
- Mark each piece that needed a correction afterward, by a supervisor, the office or the customer, and note what was wrong.
- Find the week each hire's correction rate fell to roughly the level of your experienced people.
- Group the corrections by cause: an unwritten customer rule, a software gap, a permission, or a skill.
Reading it: The week the correction rate levels off is your real ramp-up time for that role. The cause groups tell you what to fix: unwritten rules go into the workflow map, software gaps and permissions go into setup, and only the skill group is actually a training problem.
What does not fix it
- A thicker training binder
- It describes the process as someone remembered it on the day it was written. It drifts as the work and the software change, and new hires learn quickly which pages are out of date.
- Longer shadowing
- It copies one mentor's habits, workarounds included, and teaches nothing about the cases that did not come up that week.
- Hiring only experienced people
- Experience in the field does not include your customers' invoice rules, your codes or how your software is set up. Those are learned at your company or not at all.
What to try this week
- Log every question the next hire asksFor the next new hire's first month, keep a running list of each question, who answered it and how long the answer took. The list is your missing documentation, in the order people need it.
- Map one workflow as it really runsPick the workflow new people struggle with most. Walk it with the person who does it best and write every step, including the workarounds and the customer-specific rules, not the version in the old manual.
- Test what your software actually enforcesWith a test job, order or record, try to close it while skipping each required form, checklist item and signature. Note which ones truly block the close and which only remind. A new hire will find the gaps on day one.
- Set new-hire permissions on purposeCheck what a new person's role can and cannot do in each system, such as adding a line item or editing an order. A default role that is too narrow sends every exception back to someone senior.
- Separate the routine from the exceptionsTeach the path that happens every time first. Keep a short, written list of known exceptions with the person who handles each, and add to it as new ones appear.
- Review the first pieces of work within daysCheck a new person's first ten jobs, orders or entries within a few days of each, so mistakes are found before they reach the invoice or the customer.
Where do-it-yourself stops
These steps capture what your people know and make training more consistent. They do not remove the hidden steps, and written guides drift out of date as the work and the software change. The lasting fix puts the process into a tool built around your own workflow and systems, so the next step is shown and checked on screen and the retyping tricks are no longer needed. That is what a Workflow Spec designs.
Questions people ask
Why does it take so long to get new hires up to speed?
Because much of the process is undocumented and lives in a few people's heads, especially how to handle the cases that do not fit the normal path. The software rarely holds those rules, so they are learned one mistake at a time.
Will better documentation fix it?
It helps, but documents drift. It works best when the tools themselves check the steps, such as a required form that truly blocks the close instead of one that can be filled out later.
Can a new HVAC technician handle refrigerant before getting certified?
Only as a registered apprentice, closely and continually supervised by a certified technician, and for no more than two years from first registering. An informal helper does not qualify under the EPA definition.
How do we measure ramp-up time?
Track the share of each new hire's work that needs correction, week by week, and note when it falls to the level of your experienced staff. Use your own hires as the baseline; no industry association publishes a figure for it.
What if our best people have no time to train?
That is a sign the knowledge is too concentrated. Capture it once, in a workflow map and in the setup of your tools, and they stop answering the same question for every new hire.
Next step
How we fix this
This guide is how to find it and work around it. If it keeps coming back, it is rarely the only thing costing you. We come on site, find the issues costing you the most, and fix them, starting with the most pressing.
Fox & Santiago, Genesee, Idaho. We work nationwide, for clients across the United States, from our headquarters in Genesee, Idaho.
