For this scenario, Salesforce Field Service should use different Service Resource Skill Levels. The contractors differ in repair expertise, so the Repair skill should be assigned with different proficiency levels. Skill Requirements can then express the level needed for the Work Type and scheduling can distinguish their qualifications.
Salesforce favors reusable resource metadata over one-off record manipulation. When resource qualifications and availability are modeled correctly, the same information can support candidate selection, optimization, dispatching, reporting, and mobile execution without duplicating logic on individual jobs.
The alternatives address different parts of the Field Service model. Capacity represents workload volume, Preferred Resource expresses a preference rather than expertise, and excluding the less experienced contractor would unnecessarily prevent all assignment.
This keeps the workforce model reusable across scheduling, dispatching, mobile execution, and reporting and avoids encoding resource logic in individual work records.
This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Resources — Service Resource Skills; Skill Levels; Skill Requirements.
