Plan in a calendar, then record what happened.

Before you start

A missing Calendar or Time destination normally means that capability is not enabled for the organization. A missing settings leaf normally means your effective scoped claims do not permit it.

Choose the view that matches the task

Month

See timed and multi-day spans. Select a day to inspect it, click its add control for a new event, or drag across several dates to prefill an all-day range.

Week

Review local time from 07:00 through 18:00. Select a slot with the keyboard, click it, or drag vertically to prefill a timed event.

Agenda

Read a chronological list for the visible range and open an event directly. On a narrow screen, Agenda is the initial view.

Project Calendar

Open Project › Calendar for the project-context agenda and its New event composer. This is an agenda list, not the organization's Month/Week grid.

1. Move through time.Use Previous month/week, Today, and Next month/week. The organization view remembers Month, Week, or Agenda in the current browser.
2. Narrow the view.Choose Filters, then toggle Calendars, Types, or Importance. With no value selected in a group, all values in that group are included.
3. Inspect a day or event.The selected-day panel says Nothing scheduled when empty. Opening an event moves to its canonical detail page, where responses, links, editing, cancellation, and history live.

Create an organization-scoped event

1. Start from the intended date.Choose Event, use a day add control, or drag in Month or Week. The route-backed panel keeps the originating date and duration.
2. Name it and set the range.Enter Title, Starts, and Ends. Ends must be after Starts. Select All day when dates, rather than clock times, define the event; Last day is inclusive.
3. Choose the calendar boundary.Select an organization, personal, team, or project calendar that is available to you. A personal selection defaults event visibility to Busy only; other scopes default to Public details.
4. Choose Type, Importance, Visibility, and color.Visibility choices are Public details, Busy only, and Fully private. A type can default to all-day and can require, allow, or disable meeting links and participants.
5. Open More options when needed.Add a rich Description, an external Meeting link, and a Repeat value of Does not repeat, Daily, Weekly, Monthly, or Yearly. In this organization composer the Participants field is informational: it is the current member, or disabled by the selected event type.
6. Create event.The action remains disabled while the title or range is invalid, or when the selected type requires a missing meeting link.

Create a project-context event with participants and resources

1. Describe the event.Enter Event title and a rich Description.
2. Select its calendar and participants.Use Organization calendar or an available team calendar, then select organization members. Use Load more calendars or Load more participants when offered.
3. Enter the event's own time zone.Use a valid IANA value such as Europe/Berlin, then enter Starts and Ends. This zone, not the viewer's current offset, defines the stored boundaries.
4. Handle all-day dates deliberately.Select All-day event, then choose Start date and inclusive Last day. Mozaic stores a half-open interval ending at local midnight after the last day. A Berlin event on the spring DST transition therefore remains one local calendar day even though its UTC interval is 23 hours.
5. Link delivery context.Optionally choose a Linked project resource: the project, a repository, an authorized work item, or a Knowledge page. You can also attach an Agenda page and Notes page.
6. Add a safe meeting destination.The optional URL must be an absolute public HTTPS URL without embedded username/password, localhost, an IP address, control characters, or suspicious secret-like query keys such as token, password, api-key, or auth. Mozaic never fetches this URL server-side.
7. Create event.Fix any IANA-zone, range, or meeting-link error first, then choose Create event.

Respond, reveal a meeting, edit, or cancel

1. Record attendance intent.Open the event and choose accepted, tentative, or declined. A successful version-checked response reports Response recorded.
2. Authorize the destination.When an event has a meeting reference, first choose Show join destination. Mozaic authorizes the reference and displays only the destination host before it becomes a link.
3. Join without leaking the Mozaic page.Choose Join [host]. It opens a new context with noopener noreferrer and a no-referrer policy.
4. Update an event.Choose Edit event on organization detail, or Edit in project Calendar. Save with Save changes or Save update. Organization detail retains versioned Update history and Description history.
5. Cancel rather than erase.Choose Cancel event and confirm. Mozaic reports Event cancelled; RSVP, joining, and editing become unavailable, while audit evidence remains.

Run the work clock or add a manual record

Use the work clock

1. Choose Time project and Type.Only active catalog values appear. A time project can be independent or linked to a delivery project; a type preserves either Work or Pause system meaning.
2. Choose Start work.The selectors lock while the timer is active, and the strip shows the running duration and start time.
3. Use Pause and Resume.Pause switches the active timer to an available pause type. Resume switches back to work. If no active type exists for the requested kind, the switch fails without inventing a record.
4. Choose Stop.The active timer clears and Today, Week, summary, and catalog information refresh.

Add time manually

1. Select an active Time project and Type.The form prefers the last-used active values, otherwise the first available values.
2. Enter Date and Minutes.Minutes must be from 1 through 1,440.
3. Add an optional Note.The current limit is 2,000 characters.
4. Choose Add record.The command is idempotent and refreshes the time entries and weekly summary.

Review and supplement the week

1. Choose the week.Use Previous week, This week, or Next week. The summary compares recorded time with the current UI's 40-hour weekly target.
2. Read each Project / type row.Work and pause records are grouped by time project, time type, and local date. Older unclassified data is labelled Legacy / unclassified.
3. Open a day cell.Double-click it, or move with Arrow keys and press Enter. Enter 1-1,440 Minutes and an optional Note, then choose Add record.
4. Check the policy banner.It says Editing allowed, Editing allowed for [n] days, or Recorded intervals locked by organization.

Configure the time catalog, editing policy, and break versions

Set direct-edit policy

Choose Always allowed, Rolling window, or Correction request only. For Rolling window, set Editable days from 0 through 3,650, then choose Save policy. Policy changes do not erase original clock facts; revisions remain retained.

Create the allocation catalog

1. Create a New time project.Enter its Name and optionally select a Linked Mozaic project. Selecting No delivery-project link creates an independent allocation context.
2. Create a New time type.Enter its Name and choose the immutable system meaning Work or Pause. Custom names add reporting detail without changing that meaning.
3. Confirm availability.The catalog lists active status, link state, protected system types, and versions. Members can select only active values.

Create an effective-dated break-policy version

1. Policy and effective date.Enter Policy name, two-letter Jurisdiction country, Worker group, and Effective from. A new policy starts at version 1; changing an existing policy creates its next immutable version.
2. Break thresholds.Enter first and second work-hour thresholds, their required total pause minutes, the Minimum uninterrupted pause segment, and Enforcement: Warn, Block payroll/export readiness, or Require exception approval.
3. Pass validation.The second threshold must be later than the first, its pause requirement cannot be lower, and every minute value must be positive.
4. Review version.Confirm scope, effective date, both thresholds, and enforcement, then choose Create version 1 or Create version [n].

Break-policy templates are dated configuration aids, not legal advice. Confirm jurisdiction-specific policy with qualified local counsel.

Current limits and common failures

Explicitly read-only settings

• Settings › Content › Calendars is inventory only. The current API has no create, rename, archive, or default-calendar command.
• Event types supports version-checked description editing and description history only. Creation, archiving, ordering, icons, colors, and behavior changes are read-only.
• Settings › Time › Schedules is read-only. Schedule-profile creation/editing and effective-dated member workforce-profile assignments are not exposed.
• Readiness currently presents No pending corrections and Ready; it exposes no correction-review or export command. Blocking findings are defined to stop downstream export only, never clock actions.
• The current project Calendar composer creates one-off events. Recurrence selection exists in the organization composer.