MOLTARO
Register

01 · Scheduled work, explained

Know who is scheduled to work, where, and when

Work Schedule turns published working calendars, Site and Worker assignments, and append-only exceptions into one effective answer. It describes scheduled work — never attendance or physical presence.

02 · Working Schedule

One operational view from a moment to a month

Inspect Workers, Sites, or a Worker-by-Site Matrix in Day, Week, and Month views. Every interval retains its Site, local time, calendar source, breaks, and applied exception evidence.

Working Schedule Worker Week view with Warsaw Office intervals, leave, closure, and holiday exceptions Working Schedule Worker Week view with Warsaw Office intervals, leave, closure, and holiday exceptions
Real product screen · Worker week
01Workers

Follow one person's effective schedule, assigned Site, inherited or personal calendar, and exception impact.

02Sites

Read Site operating time in its governed local time zone without implying that employees are physically present.

03Matrix

Compare authorized Workers and Sites across a week while unresolved assignments stay explicit instead of becoming empty time.

03 · Working Calendars

Publish patterns without rewriting history

A calendar is a stable identity with editable Draft work and immutable Published revisions. Future revisions can be scheduled or cancelled while historical answers remain reproducible.

Working Calendars detail showing an immutable current weekday pattern with intervals and a break Working Calendars detail showing an immutable current weekday pattern with intervals and a break
Real product screen · Published calendar
01Civil time by design

Patterns use local dates and wall-clock time. The consuming Site supplies the IANA time zone and DST policy.

02Assignment inheritance

Sites select a calendar over time. Workers select a Site and can inherit that calendar or use an explicit personal one.

03Immutable publication

Publishing freezes the revision. A later change starts a new Draft, preserving the evidence needed to explain past schedules.

04 · Worker × Site matrix

Compare assignments and exceptions without losing context

Each cell keeps one Worker at one Site across the week. Ordinary hours, added or removed time, temporary moves, and explicit not-assigned states remain visible instead of being flattened into one total.

Working Schedule Matrix comparing workers across Kyiv and Warsaw sites, including schedule intervals, exceptions, and unassigned states Working Schedule Matrix comparing workers across Kyiv and Warsaw sites, including schedule intervals, exceptions, and unassigned states
Real product screen · Worker × Site matrix
05 · Effective result and governance

Every change remains attributable and deterministic

Assignments and exceptions append evidence instead of silently editing history. Access is scoped to the calendars, Workers, and Sites each actor may see or manage.

01Explicit exceptions

Remove or add scheduled time, or temporarily move a Worker to another Site, with a reason and exact local boundary.

02Deterministic precedence

Worker evidence overrides Site and Workspace evidence; removal wins over addition, then narrower and newer evidence resolves the segment.

03Time-zone provenance

IANA zones, local boundaries, resolved UTC instants, and DST diagnostics keep cross-zone work explainable.

04Scoped access

Work Schedule permissions govern native scheduling aggregates while Worker and Site visibility continues to use ordinary record security.

06 · Documentation

Operate it, integrate it, or automate it with C#

The user guide explains the screens and setup. The developer guide covers the preferred Work Schedule automation services and the advanced trusted direct-database boundary.

07 · Version 1 boundary

Scheduled time, without pretending to be attendance or payroll

Shifts, crews, published rosters, attendance, time tracking, absence approvals, payroll, overtime calculation, capacity planning, and Worker-to-user association are outside Work Schedule V1.

Back to home