Organization settings, project settings, and calendars.
We've tried to contain configuration inflation — making sensible defaults for a particular audience (engineering-minded project managers who value clarity and correctness) rather than exposing every possible toggle. When settings exist, they serve a clear purpose: enforcing organizational standards or adapting to specific project needs.
Scheduling logic should be consistent across projects. Too many toggles create hidden behavior and inconsistent outcomes.
Consequent focuses configuration on the few settings that directly affect schedule calculations: calendars and defaults.
Settings flow from organization to project. Organization settings establish defaults and constraints; project settings customize within those bounds.
Organization Level
Sets policies for all projects. Can enforce rules (no override allowed) or set defaults (projects can override). Managed by organization admins.
Project Level
Customizes settings for a specific project, within the limits set by the organization. Managed by project owners.
The standard calendar applied to new projects. Projects can customize their own calendar if organizational policy allows.
The earliest date any task can begin. Tasks without SNET constraints and no dependencies will start here.
Standard working hours per day (default: 8). Used to convert between hours and days in duration calculations.
Which days of the week are working days. Non-working days (weekends, holidays) are skipped in scheduling calculations.
Default Duration
Initial duration for new tasks (default: 1 day).
Default Dependency Type
Type for new dependencies (default: Finish-to-Start).
Invite team members to collaborate on the project. Assign roles: