Time & Calendar

GreenVee separates time-related data into two distinct concerns: work tracking (who does what, for how long, billed or not) and calendar events (meetings, site visits, calls). They overlap visually but are different objects in the data model.

The two layers

Work tracking runs from planning to actuals:

Employee Usage / Equipment Usage (planned effort on a Task)
  └── Employee Booking / Equipment Booking (reserved time blocks)
        └── Time Log (approved work session)
              └── Time Entry (start–end window inside the log)

Active Timer (live running clock) → Timer (stopped, historical) → converted into a Time Log

Alongside this, Employee/Equipment Unavailability (vacation, sick leave, maintenance, breakdown, …) and the tenant’s Working Calendar (working days, hours, and holidays) shape how much capacity is actually available for planning.

Calendar is a separate layer:

Calendar Event (meeting, visit, call)
  └── Attendees (people + participation status)

Caution

There are two calendar-like objects in GreenVee. A Project Event (part of the work plan, lives under Milestones & Gates) is a scheduled project meeting tied to the project schedule. A Calendar Event is a personal or global calendar item that may optionally reference a project, but is independent of the work plan. They look similar but are different records. See Calendar Events for detail.

Pages in this section

Page	What it covers
Planned Effort	Estimated effort per Task per Project Member (Employee Usage), bridging the plan to reality
Bookings	Time-bounded reservations of employees and equipment
Resource Unavailability	Vacation, sick leave, and equipment downtime that block capacity
Time Logs & Entries	Logged work sessions, time windows, and the approval flow
Timers & Labels	Live and stopped timers, and tagging logged time with labels
Working Calendars	Tenant working days/hours and per-day holiday overrides
Calendar Events	Meetings, site visits, and calls on the calendar

How the layers connect

Employee Usage (and its equipment counterpart, Equipment Usage) lives on a Task and belongs to a Project Member — it holds the planned effort for that person or item on that task. Bookings reserve a specific block of time for a person or piece of equipment; they link back to a Task through the Employee Usage (employee) or Equipment Usage (equipment) record. When work actually happens, it is captured in Time Logs (with one or more Time Entries), which belong to an Employee, a Project, and optionally a Task. An Active Timer lets workers capture time in real time; stopping it produces a Timer record, which can then be converted into a Time Log.

Two more layers shape how much capacity is available in the first place: Resource Unavailability marks out days an employee or piece of equipment cannot be booked, and the Working Calendar (plus per-day Calendar Exceptions) defines the tenant’s working days, hours, and holidays that scheduling is built around.

The calendar layer sits beside all of this: a Calendar Event can reference a Project, but it is not part of the work plan hierarchy.