Structuring Pay for a Two-Person Crew vs a Solo Tech
Why this matters
The moment you move a tech from working solo to working paired with a helper or a second tech, every individual-performance pay mechanic you built stops mapping cleanly onto the work. A solo tech's ticket is unambiguously theirs. A two-person crew's ticket was closed by two people who may have contributed very unevenly, and if your pay plan cannot answer "who gets credit for this job" in a way both people find fair, you will spend more time refereeing pay disputes than running the business. Get the crew-pay mechanics right once and this stops being a recurring headache.
The core problem: shared output, individual pay
Solo pay is simple because output and pay attach to the same person. Crew pay breaks that link. Two techs on a truck produce one closed ticket, one revenue number, one customer experience, but they are two separate paychecks with two separate incentive structures riding underneath. Left undesigned, this produces predictable friction: the lead tech feels they carried the helper, the helper feels underpaid for real contribution, and both start negotiating credit job by job instead of trusting the system.
Three ways to structure crew pay, and what each rewards
Split by role, not by split percentage. The lead tech and the helper are paid different structures entirely, matched to what each role actually controls. The lead is often paid a flat-rate or commission tied to the job's outcome, because they control the diagnosis, the quote, and the quality. The helper is often paid straight hourly, because their contribution is time and labor, not judgment calls. This is the simplest model to explain and the easiest to defend when someone asks why the split is not fifty-fifty: the two people are not doing the same job.
Split a shared bonus pool by a fixed ratio. Both techs share in a per-job or per-period incentive pool, divided by an agreed ratio, such as a larger share to the lead and a smaller share to the helper. This works when both people meaningfully influence the outcome (a second set of hands that also diagnoses and represents the company to the customer) rather than one being purely labor support. State the ratio in writing before the first job runs under it, not after a big ticket makes the split suddenly matter.
Pay the crew as a unit and let seniority set the internal split. The crew is quoted and measured as a single producing unit, and the pay to each member is set by their individual base rate or tier, which already reflects experience. This scales best across multiple crews because you are not renegotiating a split every time crew composition changes, but it depends on your base pay bands already being fair and documented, or the "unit pay" just launders an unfair base rate.
Matching the model to the situation
| Situation | Better fit | Why |
|---|---|---|
| Permanent lead + trainee/helper pairing | Split by role | Roles are stable and clearly unequal in judgment required |
| Two similarly-skilled techs paired for capacity, not training | Shared bonus pool by ratio | Both meaningfully drive the outcome |
| Crew composition changes often (rotating pairs) | Pay the unit, seniority sets the split | Avoids renegotiating a ratio every time the pairing changes |
| One tech is training toward independence | Split by role, with a stated timeline to solo pay | Makes the temporary imbalance visible and time-bound |
The traps specific to crew pay
Credit disputes on big jobs. The bigger the ticket, the more a vague split gets renegotiated in hindsight. Decide the split rule before the job, as a standing policy, not per job after the invoice is written. A rule applied consistently is far more defensible than a judgment call made under the influence of one large number.
The permanent helper who never gets a path to lead pay. If a "helper" role is filled by the same person for years with no route to lead-tech pay, you are not running a training pipeline, you are running underpaid labor with a temporary-sounding title. Either build a real, documented path to promotion, or be honest that the role is a permanent support position and price it fairly as one.
Double-counting individual metrics on shared work. If your pay plan also tracks something like personal callback rate or personal close rate, decide explicitly how a two-person job counts against each person's individual number. Counting a shared job's callback against only one tech's personal record, inconsistently, breeds exactly the resentment a crew-pay model is supposed to avoid.
Solo-tech spiffs that do not translate to a crew. A spiff built for a solo tech ("bonus for every maintenance plan you personally sell") needs an explicit crew version before you roll a spiff program out to paired techs, or the crew simply will not chase it because neither person is sure it is theirs to claim.
The rule that keeps all three models workable
Whichever model you choose, write down the split rule before it is tested by a real dispute, and apply it the same way regardless of which two people are paired that day. A crew-pay structure survives on consistency far more than on which specific ratio you picked.
References
- Society for Human Resource Management (SHRM), team-based incentive design guidance
- U.S. Department of Labor, Wage and Hour Division, general pay-structure guidance
- See related: Technician Compensation Plans for Service Businesses
- See related: Equal Pay for Unequal Output Decision Tree