Construction Crew Scheduling Board.

Build a crew scheduling board for Stonebriar Construction, a general contractor in Fort Worth that runs six field crews across nine active job sites, replacing the shop whiteboard that gets erased every Friday. Layout. A header bar holds a week toggle (This Week, the default, and Next Week), a job site filter dropdown, and a conflict summary that reads "1 double booking, 1 uncovered job" with red badges. The main region is the schedule grid: one row per crew, columns Monday through Saturday of the selected week. Each row header shows the crew name, foreman, trade, and headcount (for example Crew Ramirez, foreman Luis Ramirez, framing, 7). Each scheduled cell shows a chip with the job site name; empty cells show a subtle add affordance. On the right, a coverage rail lists all nine job sites with their phase and this week's scheduled crew days, marked green with 4 or more crew days scheduled, amber with 1 to 3, red when nobody is scheduled. Clicking an empty cell opens a dialog to assign a job site to that crew and day; clicking a chip lets you edit or clear the assignment. Data. Seed six crews with named foremen and headcounts from 4 to 8 (framing, concrete, sitework, finish, roofing, MEP rough-in), nine job sites with believable names (Lakeview Retail Shell, Ridgecrest Townhomes, Alta Vista Clinic, and similar) each with a phase note, and about 50 day assignments spread across this week and next. Plant two problems: Crew Ramirez is booked at both Lakeview Retail Shell and Alta Vista Clinic on Thursday of this week, and Ridgecrest Townhomes has zero crews scheduled this week even though its note says a framing inspection is coming. Behavior. Conflicts are computed, never entered: the same crew on two sites the same day flags both cells with a red border and badge, and any job with no assignments in the selected week turns red in the coverage rail. The header summary counts both kinds of conflict. Selecting a job in the filter highlights that job's cells and dims the rest. All data entry happens through the assignment dialog, but the board must look complete and current entirely from the seeded schedule. Style. Use a deep emerald accent for primary actions, assignment chips, and active states on a clean light neutral base, so the board reads like a freshly rewritten whiteboard on Monday morning.