Roles before names
Decide what the day requires: a lead who owns the outcome, the skilled positions the scope demands, and however many support hands the volume justifies. Only then match people to slots. Businesses that start from 'who is free' consistently over-staff simple work and under-staff the hard days.
One accountable lead
Every crew has a person who owns the outcome: quality, customer contact on site, the decision to stop when something is wrong. Two leads means neither, and no lead means the office finds out at the end of the day.
The lead is a crew role, not a system permission. A lead installer may have very limited application access and still be entirely responsible for the job site.
Mixing subcontractors into a crew
- The sub is assigned to the job, in a named role, like anyone else.
- Access stays scoped to that job — never widened to the whole schedule.
- Their cost lands as subcontracted work, not internal labor hours.
- Their compliance documents must be current before they are placed.
Status that reflects reality
An assignment is not a static row. It moves: assigned, confirmed by the person, on site, complete — or cancelled. Businesses that never move the status end up with a schedule that describes intentions rather than facts, which is the same as having no schedule at all.
Confirmation is the cheapest reliability upgrade available. A crew that has acknowledged tomorrow's placement is a crew that shows up to the right address.