Mobilization scheduling
Plan mobilizations per scope, in one Gantt or one list.
Mobilization periods are entered per scope on each job, with start and end dates, sequence numbers for re-mobilizations, and status (planned, confirmed, in progress, completed, cancelled, postponed). The Schedule tab on each job shows the periods inline; the company Gantt nests jobs over scopes over crew members in a single timeline so a project manager can see who’s where, and when, across the whole portfolio.
- Per-scope mobilization periods with start and end dates, sequence numbers, and status.
- Job-level Schedule tab and a company-wide 3-level Gantt: jobs over scopes over crew members.
- KPI cards roll up planned, confirmed, in-progress, and completed counts per filter.
Crew assignments and skill matching
Assign crews by skill, with the AI pre-screening for fit and conflicts.
Crew assignments include worker counts and durations; mobilization dates on the assignment auto-sync from the scope’s mobilization period. Skill definitions and per-employee proficiency ratings are entered once by the project manager, with skill requirements set per MasterFormat code or overridden per scope. With those in place, the AI scores every crew member 1 to 5 against the requirements: ask for a crew recommendation and it returns the best-matched crews, ranked by match percentage, with double-booked members flagged before the assignment is committed.
- Crew assignments with worker count, duration, and mobilization dates that auto-sync from the scope’s mobilization period.
- Per-employee skill ratings (1 to 5) and skill requirements set per MasterFormat code or per scope.
- AI recommendations rank crews by match percentage and flag scheduling conflicts before assignment.
Mobilization workflow
Mob types, sequence numbers, and crew dates that move together.
Each mobilization period has a type (standard, remobilization, partial, weather delay, phased) and a sequence number on the scope, so the second mob on a scope is unambiguously sequence 2 instead of guesswork from the calendar. When a mobilization period is created or updated, the linked crew assignment’s mobilization dates update with it, so the Gantt and the assignment list reflect the same plan.
- Five mobilization types: standard, remobilization, partial, weather delay, phased.
- Sequence numbers on each scope’s mobilization periods so re-mobilizations are explicit and ordered.
- Crew assignment dates auto-sync when the linked mobilization period changes.
Visibility and conflicts
Everyone sees the schedule. Conflicts surface in the Gantt.
The Schedule tab and the company Gantt are visible to project managers, foremen, crew leads, and crew members in any browser. Project managers add and edit; everyone else views read-only. Overlapping crew assignments surface as conflict flags on the Gantt bars, so a double-booking shows up at planning time instead of after the foreman has driven to the wrong job.
- Schedule tab and company Gantt visible to all roles, read-only for non-PMs.
- Overlap detection: conflict flags on Gantt bars when a crew member is assigned to two scopes at the same time.
- Same data on a phone browser as on a desk monitor.
Weekly outlook
Ask “what does next week look like?” and the scheduling agent answers.
Construction PM’s scheduling agent answers questions like “what does next week look like?” and “who is mobilizing where?” Project managers enter the schedule and the crew assignments; foremen log labor through Connecteam daily reports and the field tool. The agent reads that data and returns a structured response: upcoming mobilizations, assigned crews, worker counts, forecast hours per scope, and any unassigned scopes that need attention. Forecast hours are simple averages from the last few weeks of labor history on each job, so the answer reflects how crews have been working rather than just the planned hours on the schedule.
- Upcoming mobilizations with dates, assigned crew, and worker count.
- Per-scope forecast hours grounded in recent labor history (averages from past weeks).
- Unassigned scopes flagged so a project manager can fix gaps before the week starts.