Home
Optimization Levels in Dusk FSM

Dusk FSM Optimizer Contractor Setup

## Dusk FSM Optimizer Contractor Setup

This article explains how to prepare **Contractor** profiles so the Routing Optimizer can assign, route, and cost jobs accurately. It covers the minimum fields to capture, why they matter, recommended defaults, and a quick checklist to confirm readiness.

---

### What the optimizer needs from each person

The optimizer builds day plans using a person’s **where**, **when**, **what**, and **cost**.

| Field                                       | Why it matters                                                             |
| ------------------------------------------- | -------------------------------------------------------------------------- |
| **Shift** (start, end)                      | Defines available working minutes, enables legal and overtime checks.      |
| **Region** (polygon or assigned region)     | Limits eligible jobs, reduces cross-region travel, enables zone policies.  |
| **Home Address**                            | Possible **start** or **end** of day, improves first-leg travel accuracy.  |
| **Base Location** (Depot, Work base)        | Alternative **start** or **end** of day, required for depot-based work.    |
| **Skills**                                  | Ensures only qualified people are considered.                              |
| **Certified** flag, **Proficiency Level**   | Enforces regulatory work, improves duration estimates and SLA reliability. |
| **Hourly Rate** and optional **Skill Rate** | Enables cost-aware planning, overtime costing, contractor pricing.         |

> **Foundation Profile (recommended rule):** require Shift, Region, at least one Start Location (Home or Base), and Skills for every Staff or Contractor. Encourage Hourly Rate and both start locations for best results.

---

### Start and End Policy

Start/End Policy tells the optimizer where a person starts and finishes the day.

* **home**: start at Home Address.
* **work**: start at Base Location.
* **home\_or\_work**: optimizer chooses the better start for the first job, while keeping appointments feasible.
* **same\_as\_start**: end where you started. Variants: **home**, **work**.

**Recommended defaults**

* **Contractors** with depot processes, vehicles or inventory: **work** start, **same\_as\_start** end.
* **Contractors** who travel from home: **home** start, **home** end.
* Allow account-level defaults, allow per-person overrides.

---

### Skills, Certification, and Level

* **Eligibility**: a person must have every required skill for the job.
* **Certification**: if required, the person must be certified, not expired.
* **Proficiency Level**: use level to adjust expected duration, for example:

* Level 1 = 1.15× base duration,
  * Level 2 = 1.00×,
  * Level 3 = 0.90×,
  * Level 4 = 0.85×,
  * Level 5 = 0.80×.

This makes ETAs, SLA compliance, and capacity far more accurate.

---

### Region setup

Regions can be defined as **polygons**. For each person the optimizer checks whether a job lies inside their region.

* **Hard policy**: outside polygon is ineligible.
* **Soft policy**: allowed with a cross-region penalty, optionally limited per day.
* **Border buffer**: add a small tolerance so jobs near the edge are not excluded by rounding.

---

### Cost handling

* **Hourly Rate** drives cost per minute.
* **Skill Rate** (optional) applies a premium when a specific skill is used, useful for contractors.
* **Overtime**: configure a rate or penalty after shift end.

Use cost in “Cost Saver” profiles, keep it secondary in “SLA First” profiles.

---

### Step-by-step: Contractor setup

1. **Enter Home Address**, confirm the map pin is correct.
2. Set **Region** from your polygon list.
3. Choose **Base Location** if the contractor uses a depot, otherwise leave blank.
4. Select the **Shift** the contractor works.
5. Provide **Hourly Rate**, optionally **Skill Rate** per skill.
6. Add **Skills**, tick **Certified** where required, set **Proficiency Level**.
7. Save.

**Minimum for contractors:** Shift, Region, Home **or** Base, Skills.

![Contractor Optimizer Setup](https://help.duskmobile.com/uploads/markdown/20250917-222810-313.png)

*Contractor profile fields used by the Optimizer.*

---

### Readiness indicator

Shows a small badge on each person:

* **Ready**: all four Foundation fields present, icons visible.
* **Partial**: missing one item, amber, show what to add.

This helps admins complete data before running optimization.

---

### Best-practice defaults

* **Start Policy**

* Staff: **work**, End Policy **same\_as\_start**.
  * Contractors: **home**, End Policy **home**.
* **Lock Window**: 45 minutes, protects near-term stops from reshuffle.
* **Region Policy**: Hard for appointment/SLA customers, Soft with penalties for campaign work.
* **Duration multipliers**: use the level table above.
* **Breaks**: configure fixed or flexible breaks in the shift where needed.

---

### Data quality checklist

* Home and Base are geocoded to lat, lon, confidence looks correct.
* Region polygon assigned, border cases verified.
* Shift times in the correct timezone.
* At least one Skill per person, Certification expiry dates where required.
* Hourly Rate entered, Skill Rate used for premium skills if needed.

---

### Troubleshooting

* **Optimizer skips a person**

* Check Region membership, Skills, Certification, and Shift overlap.
* **Routes start in the wrong place**

* Review Start Policy and whether Home or Base is missing.
* **Overtime appears unexpectedly**

* Verify shift end, travel time from the chosen start, and duration multipliers.
* **Too many cross-region jobs**

* Switch Region policy to Hard, or raise the cross-region penalty.

---

### FAQs

**Do I need both Home and Base?**
No, at least one is required. Having both enables the **home\_or\_work** Start Policy for better first-leg choices.

**What if we do not track costs?**
Set Hourly Rate later. The optimizer will still run SLA-first profiles; cost-saver profiles will be less effective.

**Can a person belong to multiple Regions?**
Yes. Add multiple polygons, the optimizer will consider jobs in all assigned areas.

**How are skills matched for multi-skill jobs?**
If the job requires A **and** B, the person must have both. If it accepts A **or** B, the optimizer picks the best match.

---

### 🔗 Related Articles

* **[Step-by-step: Staff setup](https://help.duskmobile.com/article/Optimization-Levels-in-Dusk-FSM/Dusk-FSM-Optimizer-Staff-Setup "Step-by-step: Staff setup")**

Updated on September 23, 2025

Dusk FSM Optimizer Contractor Setup

Need Support?

Error

Delete Article