Join the LadVen OS testing programRequest a demo
Skip to main content

Calendar

The LadVen OS calendar shows work commitments in time: task deadlines, personal and team reminders, customer-related events, and actions that should not get lost in chats or task lists.

Use it as a day, week, and month plan. The calendar does not replace tasks, CRM, or documents. It shows when to return to an action and who owns the next step.

Where to Find It

Views and sources — conceptual guidance, not UI evidence

Weekly calendar: meetings, calls and reviews laid out by day and hour.

The main route is Calendar (/calendar). The page supports:

  • day, week, and month views;
  • personal and team scope;
  • source filter: plan, deadline, reminder, AI action;
  • reminder status filter: all, drafts, active, or snoozed;
  • Show completed toggle: brings completed and canceled reminders, plus closed task rows, back into the calendar in a muted style;
  • Without time block for reminders without an exact time;
  • linked record card when an item belongs to a task, CRM, document, project, or client.

When to Use the Calendar

Personal plan and linked records — conceptual guidance, not UI evidence

Use the calendar to check personal workload, review team deadlines, move a reminder, open a linked task or CRM record, create a personal reminder, or return to an action at the right time.

Use it to:

  • check personal workload for a day or week;
  • see team deadlines and reminders;
  • move a reminder to another time;
  • open a linked task, inquiry, document, or client record;
  • create a personal reminder without an extra task;
  • return to an action that must happen at a specific moment.

If the work needs a result, assignee, and acceptance, create a task. If you only need to return to a question at a specific time, a reminder is enough.

Views and Filters

Views and sources — conceptual guidance, not UI evidence

Use the day view for detailed scheduling, the week view for workload and deadline control, and the month view for larger commitments.

Use Today to return to the current working date. If no events are visible, check the filters, selected period, and whether personal or team mode is active.

In month view, a day cell shows one card and uses N more when additional items exist. Select it to move to that date's day view and see the remaining items. This does not mean that records were deleted or filtered out; check the active filters and scope first.

Calendar items can come from work plans, deadlines, reminders, and AI actions. Filter sources and reminder statuses when you need a cleaner operational view.

Event sources

Views and sources — conceptual guidance, not UI evidence

Different sources can appear in the calendar:

  • planned work items;
  • deadlines of tasks and linked objects;
  • personal and team reminders;
  • AI actions, if they are configured for the work scenario.

The source filter helps remove clutter. For example, a manager can look only at deadlines and team reminders, while an assignee sees their own tasks and personal signals.

Reminders

Reminder lifecycle — conceptual guidance, not UI evidence

Create a reminder when an action does not need a separate task but must appear at the right moment: call a client, check a reply, return to a document, clarify status, or prepare for a meeting.

A useful reminder has:

  • a clear title;
  • a start time or signal;
  • an assignee when it is not only personal;
  • a short comment with context;
  • a link to the task, CRM record, or document when the action belongs to another work object.

Items without time stay in the Without time block. Use it as a draft area, but do not leave important commitments there for long.

Statuses and Moving Items

Reminder lifecycle — conceptual guidance, not UI evidence

A reminder can be draft, active, snoozed, done, or canceled. Draft is useful for an idea without exact time. Active should lead to action. Snoozed should have a clear reason for the move.

In day and week views, reminders can be moved in time. Before moving one, check whether it changes a client agreement, task deadline, or another participant's work. If it changes a commitment, record the reason in the linked object.

Recurring and AI Actions

Recurrence and safe AI — conceptual guidance, not UI evidence

Use a recurring schedule for repeated commitments: daily, weekly, with interval and weekdays. Recurring reminders fit report checks, meeting preparation, calling routines, and status reviews.

Check the timezone on a recurring reminder: it determines the local trigger time. When a team spans timezones, record the expected local time in the title or comment rather than compensating by changing the deadline.

Use AI actions only for clear and safe scenarios: remind, prepare a prompt, collect context, or send a signal to a work chat. Do not put private data, passwords, tokens, or client materials into a prompt unless the process allows it.

Personal and Team Mode

Personal plan and linked records — conceptual guidance, not UI evidence

Personal mode shows commitments related to you. Team mode helps a manager or coordinator see shared deadlines, assigned reminders, and workload risks.

Before moving a team reminder, check whether it affects a client, task deadline, or another department. If the move changes an agreement, record the reason in the linked object.

Linked Records

Personal plan and linked records — conceptual guidance, not UI evidence

When an item is linked to a task, opportunity, document, or customer record, open that record and continue the work there. The calendar shows timing; decisions, files, comments, and acceptance belong in the work object.

The linked-record card may briefly show a loading state or an access-unavailable marker. This does not mean the record was deleted: check permissions and open the work object itself instead of creating a duplicate.

Do not put passwords, tokens, internal technical URLs, or private customer data into calendar titles or comments.

Good Practices

Reminder lifecycle — conceptual guidance, not UI evidence

  • Plan the week by tasks and deadlines, and the day by concrete actions.
  • Do not turn the calendar into a duplicate of every task: keep only events, deadlines, and reminders there.
  • For an overdue action, check the linked object first, then move the time.
  • Use team mode for workload control, not for micromanaging every step.
  • Review the Without time block at the end of the day so drafts do not become lost promises.

Manager Control

Reminder lifecycle — conceptual guidance, not UI evidence

A manager should look at the quality of commitments, not only at the number of events:

  • overdue active reminders without a comment;
  • important items in Without time;
  • frequent moves of team reminders without a reason;
  • AI actions with unclear wording;
  • calendar events that duplicate tasks and do not help the assignee.

When the calendar shows a risk, open the linked task, CRM record, or document and record the decision there.

Safe Demonstrations

Recurrence and safe AI — conceptual guidance, not UI evidence

For team training and screenshots, use only demo tasks, customers, projects, and documents. Calendar examples must not expose real phone numbers, addresses, private URLs, customer names, financial terms, passwords, tokens, or internal technical names.

Related Scenarios — Conceptual guidance, not a UI screenshot or state evidence. Conceptual guidance, not a UI screenshot or state evidence.