Time and Calendar
Working Calendars
How GreenVee defines a tenant's working days and hours, and how per-day exceptions like holidays override them.
Every schedule in GreenVee — Gantt bars, milestone dates, resource utilization — is built on top of a Working Calendar: the tenant-wide definition of what counts as a working day and a working hour.
Working Calendar
Section titled “Working Calendar”There is exactly one Working Calendar per tenant.
| Field | What it stores |
|---|---|
| Working days per week | How many days count as working days (default 5) |
| Working hours per day | How many hours count as a working day (default 8) |
| Weekend days | Which days of the week are treated as weekend (default Saturday and Sunday) |
Weekend days are shown as shaded columns on the Gantt, and duration calculations (e.g. spreading planned effort across a task) use the working days/hours to figure out how much time is actually available.
Calendar Exception
Section titled “Calendar Exception”A Calendar Exception is a per-day override of the Working Calendar — typically a public holiday, a special non-working day, or a day with reduced hours.
| Field | What it stores |
|---|---|
| Date | The specific day being overridden |
| Is working | Whether this day counts as a working day at all |
| Working hours | Optional override of the number of working hours on this day |
| Label | A short note (e.g. “Public Holiday”) |
Calendar Exceptions feed into the same scheduling calculations as the Working Calendar — a task’s duration or a milestone’s date will skip a day marked as non-working, or use a reduced hour count on a day with a partial override.
Related pages
Section titled “Related pages”- Planned Effort — cadence and effort calculations that rely on the working calendar
- Resource Unavailability — individual employee/equipment gaps on top of the tenant-wide calendar