There is no universal answer to how many roofing shirts per crew member. Calculate the issue quantity from the number of branded-shirt wear days before the employee's next reliable laundry opportunity, then add a documented backup only when the company has a real reason for one. Apply the calculation by role and shirt version, not as one blanket number for the whole roster.
This article owns the rotation calculation. The small-crew ordering guide covers vendor-ready roster and proof steps, while the year-end audit reconciles the full program.
Use a rotation formula, not an industry guess
Start with this planning structure:
base rotation = branded-shirt wear days before the next reliable laundry opportunity
planned issue = base rotation + approved contingency
The contingency is not automatically one shirt. Define why it exists: delayed laundry, an occasional additional customer-facing day, or another recurring operational situation the company has observed. Avoid stacking several vague “just in case” extras.
This formula is an internal inventory method, not a promise about garment lifespan, cleanliness, or job conditions. Employees and managers still follow the actual product care source and company policies.
Count branded-shirt wear days by role
Ask how many days in the cycle each role is expected to use this particular company shirt version. An estimator may use a customer-facing version on appointment days and a different approved version at other times. A project lead may use the core crew version across most of the week. A warehouse employee may have a different schedule.
Do not count calendar days when the shirt is not assigned. Do not assume every employee works the same pattern. Use an average recurring schedule and record known variations.
Create a role table:
| Role/version | Wear days before laundry | Laundry opportunity | Contingency reason | Planned issue |
|---|---|---|---|---|
| Estimator version | Company input | Company input | Document | Calculate |
| Field crew version | Company input | Company input | Document | Calculate |
| Project lead version | Company input | Company input | Document | Calculate |
Populate the table with the company's real process rather than copying numbers from an example online.
Define the laundry opportunity honestly
A “weekly laundry” label is not enough. Identify when clean shirts reliably return to the wearer. If employees launder shirts themselves, ask when that normally occurs under the company routine. If the business manages laundering, use the collection and return schedule.
The interval determines rotation. An employee wearing the same version four days before a reliable wash needs a different base than someone wearing it two days before the next wash.
Do not prescribe wash settings here. Each product's current care label controls laundering. The roofing uniform care guide owns the care and observed-condition workflow.
Add contingency for a named event
A backup can reduce disruption, but it should have a defined purpose and owner. Examples of questions to ask include:
- Does the role regularly add an unscheduled customer-facing day?
- Does the company laundry cycle occasionally return after the next assigned shift?
- Is one clean spare kept centrally rather than assigned to each employee?
- Are role-specific shirts difficult to reassign when staffing changes?
Choose between an individual contingency and shared inventory. A central size-based reserve may serve some teams better than automatically issuing an extra to every person. Keep shared stock in its own record so it is not counted as an employee's rotation.
Do not justify contingency with an unsupported claim that roofing shirts always wear out at a certain rate. Replacement for observed condition is a separate process.
Separate role versions in the math
If one employee receives both an estimator polo and a field crew shirt, calculate each version from its actual wear cycle. Do not double a full-week number for both categories.
For example, suppose a mixed-role employee normally uses the customer-facing version on two appointment days and the crew version on three production days before the next laundry opportunity. The base rotation is calculated as two of the first version and three of the second, before any documented contingency. The example shows the method; it is not a recommendation for every employee.
Record the approved artwork and current product reference beside each version. Two shirts in the same color may not be interchangeable if they carry different role labels, company copy, or product-specific care information.
Handle new hires and uncertain schedules separately
Do not inflate every current employee's issue quantity to cover possible hiring. Maintain projected positions outside the named active roster. When a hire is confirmed, assign the appropriate role version and calculate from that person's expected schedule.
For seasonal hiring, use the dedicated seasonal roofing uniform checklist. It covers pre-arrival sizing, issue records, in-season changes, and offboarding rather than changing the base calculation.
If a schedule is genuinely uncertain, choose a temporary starting issue with a review date. Record the assumption and owner. An explicit pilot is more manageable than quietly converting a guess into permanent policy.
Convert the role result into a named roster
Once the calculation is approved, assign quantities by employee, size, role version, and status. A useful roster row includes:
- employee or internal identifier;
- primary role and schedule;
- approved shirt version;
- confirmed current size source;
- base rotation quantity;
- contingency quantity and reason;
- shared inventory allocation, if any;
- review date and approver.
Keep confirmed, projected, and unresolved quantities separate. A total that blends them is easy to misread during ordering.
The guide to ordering roofing shirts for a small crew takes the named roster through product verification, artwork approval, and final reconciliation.
Review triggers
Recalculate when the laundry interval changes, an employee changes role or schedule, the company introduces a new uniform version, or repeated shortages show that the documented contingency does not match reality.
Do not redesign or recalculate merely because the calendar changed. The year-end audit can confirm whether the existing policy still matches records, but it should not replace the role-based method.
Keep observed replacement events separate from issue quantity. A damaged item may need replacement without changing the standard rotation. Several untracked losses may require an operational response, not an automatic increase for the entire crew.
Decision worksheet
- How many days is this exact version worn before clean shirts reliably return?
- Is the schedule confirmed for this role and employee?
- What specific event justifies a contingency?
- Should that contingency be individual or shared by size?
- Are different role versions calculated separately?
- Which assumption triggers a future review?
The resulting number is defensible because every unit has a reason. After the roster and quantity policy are approved, managers can compare the PrintFrenz roofing collection with current needs and verify all product and order facts at decision time.