Frequently Asked Questions

If parts arrive late and a stage is delayed, simply drag the corresponding allocation block to the new start date. The dependency-aware scheduling engine will automatically compute the required gap-shift and cascade all downstream stages forward in time. If this delay pushes any component past its delivery date, you'll receive an immediate warning via the Deadline Violation Modal — giving you the choice to force the schedule or cancel the operation.

EDF is a well-known priority scheduling heuristic that processes tasks in order of their deadline — the closest deadline gets scheduled first. In HeadOps, when you move a component, the engine identifies all affected components, sorts them by deadline, and greedily assigns each one to the earliest available team slot. This ensures that the most time-critical orders always get priority access to your teams.

Yes. By default, all stages operate on a 5-day working week (Monday–Friday). However, individual stages can be toggled to a "6-day" mode (Monday–Saturday) directly from the Stage Popover on the timeline. When you switch a stage to 6-day mode, HeadOps instantly recalculates its end date to include Saturdays as working days.

The "Reschedule All" button triggers a global optimization that recomputes your entire factory schedule from scratch. It eliminates every team conflict, fills scheduling gaps, and repacks the timeline using the EDF algorithm. Before applying changes, you see a preview showing conflicts resolved, gap days reclaimed, and any deadline violations — so you can make an informed decision before committing.

HeadOps supports workspace-scoped public holiday calendars. When a stage has "observe holidays" enabled (the default), the scheduling engine skips holiday dates when calculating end dates. This means a 5-day stage that spans across a holiday will extend by one calendar day without consuming an additional working day. You can manage holidays in Settings → Public Holidays.

HeadOps has a built-in conflict detection engine that continuously monitors all team allocations. If two stages assigned to the same team overlap in time, the timeline immediately renders a red conflict overlay on the affected blocks. You can then either manually adjust the schedule or use the "Reschedule All" feature to automatically resolve all conflicts.

When you need to schedule a new component, the Auto-Allocation Wizard evaluates up to 100,000 permutations of team assignments. For each stage in the component, it considers all teams that are linked to the appropriate stage type, then tests every combination to find the one that produces the earliest possible completion date. It respects existing allocations to prevent conflicts and warns you if the best result exceeds the delivery deadline.

Yes. Teams have a many-to-many relationship with stage types. In the Settings page, you can link each team to as many stage types as they're capable of performing. This ensures the Auto-Allocation Wizard considers them for all relevant work, maximizing flexibility in your scheduling.

Every HeadOps account belongs to a Workspace, which acts as a secure data boundary. All projects, teams, stage types, and holiday calendars are scoped to the workspace. Row Level Security (RLS) is enforced at the PostgreSQL database level, meaning even API-level access is restricted to data within the user's workspace. There is no possibility of cross-tenant data leakage.

HeadOps currently supports Google OAuth as the primary authentication method, powered by Supabase Auth. When a new user signs in for the first time, a workspace is automatically provisioned for them, and their profile is created with the "admin" role.

Yes. Workspace admins can invite new users by email with one of three roles: Admin (full access), Editor (can modify projects and schedules), or Viewer (read-only access). Pending invitations can be viewed and revoked from the Settings page.

Absolutely. HeadOps includes a patch-based undo/redo engine that records every allocation change. The Undo and Redo buttons are always available in the Planning Header toolbar. Reschedule operations (including cascading changes to multiple allocations) are recorded as a single undoable batch, so you can roll back an entire cascade with one click.

Yes. The Teams page provides an alternative Gantt view organized by team rather than by project. Each team has its own row showing all allocations assigned to them across all projects. You can drag allocations in this view as well — the same rescheduling engine powers both views.

Yes. HeadOps uses Supabase Realtime for live data synchronization. When any user in your workspace makes a change — creating a project, moving an allocation, or adding a team — the update propagates instantly to all connected browsers. No manual refresh is ever needed.