Schedule the crew week
The scheduling board answers Monday's first question — who is where today? — before the phones start. It plans crew against field work orders (the dispatchable pieces of a job), and the plan isn't a wall chart that dies at 7am: the same assignments show on the field side's schedule, and when the foreman opens the day's timecard, the crew rows arrive pre-filled from what you scheduled.
What you need
- A crew roster — the board's worker rail is the active roster.
- At least one project with a field work order to schedule against. A job with no FWOs yet has nothing to put crew on.
Plan the week
- Scheduling (
/scheduling). Pick Week view; the board shows the week's days against the work orders in play. Day view is the same board zoomed to one day. - Drag a worker from the rail onto a work order's day. That's an assignment. Drag it to another day to move it; remove it if the plan changes.
- Scheduling the same crew for several days? Set one day the way you want it, then use the fill action to carry that crew across the rest of the range — it skips workers already placed, so it layers instead of duplicating.
- Watch the capacity picture as you go: a worker stacked on two jobs the same day is a promise someone breaks at 6am. Resolve it on the board, not at the gate.
Where the plan lands
- The field sees it — the schedule tab on the Field workspace shows the crew what's planned, day by day.
- Timecards start from it — the foreman's daily entry pre-populates from the day's assignments, so a scheduled day is confirmed in seconds instead of rebuilt from memory.
Common mistakes
- Scheduling in someone's head. The unwritten plan can't pre-fill a timecard and can't show a conflict. If it's not on the board, the board's downstream value is zero.
- One giant work order for the whole job. If everything is "Job — general", the board can't say what the crew is actually doing. Break the work into orders that match how you dispatch.
- Leaving ghosts. When a day slips, move the assignments — stale ones keep pre-filling timecards with a crew that wasn't there.
See also
This is how STrOp works
The data flows you read about here are how the platform threads bid, execution, billing, and closeout. Single pipeline. No re-keying.
Request beta access →Last updated 2026-08-20.