A calendar tells Syncify when work can happen. Durations and lags are scheduled through working time, so calendar mistakes can look like duration or logic mistakes.

Check the calendar actually assigned

Select an activity and inspect Calendar in Details, or add the Calendar column to the grid. The activity’s assigned calendar controls its working time. Check several activities if a project uses different crews, shifts, or workweeks.

The schedule’s default calendar is the default choice for work that uses it; changing a default is not a substitute for reviewing existing activity assignments. Resource calendars do not override activity calendars or drive task dates in Syncify.

Open or create a calendar

In Edit mode, open the calendar controls in the schedule’s editing toolbar. The menu distinguishes calendars used by the schedule and other available calendars. Open a calendar to review it, or use the available create/copy action to start from an existing pattern.

You can also manage reusable calendars under Assets → Calendars. Scope matters: a workspace calendar can serve several projects. Duplicate or copy a shared calendar when the variation should apply only to one project or group of activities.

Set the weekly Work Schedule

1. Open the calendar and choose Work Schedule.
2. Review which days are working and nonworking.
3. Set the work periods for each working day. Separate periods can represent a lunch break or split shift.
4. Give the calendar a name that describes the pattern, such as “5-day, 8-hour” or “Weekend shutdown crew.”
5. Save the calendar.

For example, an eight-hour day could contain 08:00–12:00 and 13:00–17:00. A Friday afternoon start will use the remaining working hours and then continue at the next working period; it does not consume a weekend merely because time passes.

Add holidays and exceptions

Open Exceptions to set dates that differ from the normal week. Use a nonworking exception for a holiday or shutdown, and custom working hours for an exceptional workday or shortened shift.

Check the date and hours before saving. A missing holiday can bring a finish forward; an accidental nonworking exception can push it later. Imported calendars may already contain exceptions, so review before adding duplicates.

Unsaved changes in the calendar dialog are separate from ordinary grid edits. Use its Save or Create Calendar action to keep them; cancelling the dialog discards the pending calendar changes.

Assign and calculate

Assign the intended calendar to the relevant activities, then calculate the schedule as appropriate. Inspect a short activity that crosses a weekend or holiday to verify the pattern.

A longer elapsed span does not necessarily mean a longer working duration. Two activities with the same working duration can finish on different dates because they start at different times or use different calendars.

Calendar choices affect lag too

Relationship lag uses the predecessor’s activity calendar. If a seven-day predecessor feeds a five-day successor, first apply the lag on the predecessor calendar, then account for the successor’s working periods. See Relationships when investigating a surprising handoff.

Imported calendars

P6 XER imports include working patterns, exceptions, and duration-conversion values. Microsoft Project XML preserves more calendar detail than binary MPP. MPP import reconstructs a standard weekly pattern, so it should not be your preferred format for unusual shifts.

Microsoft Project base-calendar inheritance is not fully represented. Check the imported workweek even when its name looks familiar. Read the Microsoft Project calendar limitations before relying on the result.

Date and timezone meaning

Schedule dates represent the project’s scheduling dates, regardless of the viewer’s timezone. Do not manually offset start or finish dates because a reviewer is in another region. If a date looks wrong, check working hours, status date, constraints, and source-file settings before making a timezone adjustment.