> ## Documentation Index
> Fetch the complete documentation index at: https://docs.helmkit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Day Notes

> Add day-level operational context to calendar, agenda, and timeline views in Helm

Day notes let your agency team pin short operational context to a day, a date range, or a repeating schedule. They appear directly in Helm's scheduling views, so the team sees important context before opening individual runs.

## When to use day notes

Use day notes for information that applies to the day itself or to multiple runs in the same period, such as:

* Dock or pickup point closures
* Platform changes
* Weather or safety alerts
* Holiday staffing reminders
* Temporary operational instructions

If the discussion belongs to one specific departure, use [run comments](/features/run/comments) instead. Comments stay attached to a run. Day notes live on the calendar.

## Where day notes appear

Day notes appear in all three scheduling surfaces:

* **Calendar** — Above the day's runs as colored note bars
* **Agenda** — In a sticky day-notes row above the list of runs
* **Timeline** — In the note band for the selected day

Selecting a note opens the full note dialog. On desktop, hovering also shows a quick preview with its category, date range, recurrence, and author.

## Create a day note

You can create day notes from the calendar header or directly from a day column.

<Steps>
  <Step title="Open Calendar">
    Go to Helm's main calendar view.
  </Step>

  <Step title="Start a new note">
    Use the **New Event** split-button menu and choose **Day note**, or click the
    **+** button next to a day header.
  </Step>

  <Step title="Add the note details">
    Enter a short title, an optional description, and choose a category.
  </Step>

  <Step title="Set the date range">
    Choose the start day and end day. A single note can cover one day or span
    multiple days.
  </Step>

  <Step title="Choose whether it repeats">
    Set the note to repeat daily, weekly, or monthly if the same operational
    context should keep appearing.
  </Step>

  <Step title="Save">
    The note appears immediately in the visible scheduling views.
  </Step>
</Steps>

## Categories and date ranges

Each day note has a category that controls how it is styled in the calendar:

* **Closure** — For closures or unavailable locations
* **Platform** — For logistics changes such as docks, platforms, or meeting points
* **Alert** — For urgent operational warnings
* **Other** — For general scheduling context

The start and end days control how long the note stays visible. A non-repeating note can cover multiple consecutive days. Repeating notes keep the same span on each occurrence.

## Repeating notes

Day notes can repeat on three cadences:

* **Daily**
* **Weekly**
* **Monthly**

Repeating notes can run indefinitely or stop on a chosen end day. This is useful for recurring closures, weekly reminders, or regular operational constraints that the team should keep seeing in the schedule.

## Edit one occurrence or future occurrences

When you open an existing repeating note, Helm lets you choose how broad the change should be.

* **This day only** updates or removes a single occurrence without changing the rest of the series
* **This and future** updates or removes the selected occurrence and every future occurrence in that series

For non-repeating notes, edits apply to the note as a whole.

## Show or hide day notes

If you need a cleaner schedule view, you can temporarily hide day notes.

* Open **Display options**
* Toggle **Show day notes**
* Use `Shift+M` as a keyboard shortcut

When day notes are hidden, Helm still shows a small indicator on days that have notes. Click that indicator to turn day notes back on.

## Permissions

Day notes are available to agency users working inside an active organization.

* Agency members can view and create day notes
* The note's creator can edit and delete it
* Organization admins and owners can also edit or delete other members' day notes
* Guides do not have access to day notes

## Day notes vs comments

Use **day notes** when the information belongs on the schedule and may affect multiple runs in the same date range.

Use **comments** when the information belongs to one specific run and should stay in that run's activity history and discussion thread.