Adding Notes to the Seasonality Page

What notes are for

The Seasonality page shows what happened — revenue by day, weather, events, holidays. It doesn't show why. Notes are the qualitative layer: the record that a spike came from a festival, that a bad Tuesday was a closed entrance, that a weather correlation is coincidence rather than cause.

The panel sits at the very bottom of the page, headed Notes — "Qualitative data and context for anomalies."

Adding a note

1. Open the form

There are two ways in, and they open the same panel:

• Scroll to the Notes panel at the bottom and click + Add note
• Click Actions (top right of the page) and choose + Add note

A drawer titled Add New Note slides in from the right.

2. Fill in the four fields

All four are required — the red asterisk marks each one.

Note Free text, up to 500 characters. A live counter sits under the box (0/500). Write the context a colleague would need three months from now, not a restatement of the number they can already see. "Downtown street festival closed Water St, drove overflow parking" beats "revenue was high."

Scope — who this note applies to A three-way toggle:

Defaults to City, pre-filled with whichever city the page is currently filtered to. Under Locations, sites are listed with their city appended — e.g. Keystone Lot - Milwaukee, WI.

Date — when this applies Toggle between Single date and Date range. Defaults to Single date, pre-filled with today. Click the field to open a month calendar; use the ‹ › arrows to change month.

Note Type Two cards: Positive ("Good news or improvements") or Negative ("Issues or concerns"). Nothing is selected by default — pick one, and the card fills green or red.

3. Save

Click Add note. A green "Note added." toast confirms it, the drawer closes, and the note appears in the Notes panel immediately. Cancel discards everything.

Working with existing notes

Each saved note shows as a card: a coloured left edge and thumb icon (green up / red down), the date, the scope it was filed under, and the note text. A count sits below the list — "Showing 1-1 of 1."

Two controls sit at the top-right of every card:

• ^ chevron — collapses the card to just its header. Useful once a busy month has a dozen notes.
• ⋮ kebab — opens Edit and Delete.

Edit reopens the same drawer, retitled Edit Note, with every field pre-filled and the button changed to Save changes. Scope, date and type can all be changed after the fact, not just the text.

Delete raises a confirmation — "Delete note. Are you sure you want to delete this note?" — with Cancel and a red Delete. There is no undo and no trash, so treat it as permanent.

Where your note will and won't appear

This is the part that trips people up. The Notes panel is not a global list. It shows only notes matching the page's current filters.

• Month. Notes appear only in the month their date falls in. A note dated 31 August is invisible from the July view. (Verified: switching to July 2026 showed "No notes yet" while the August note existed.)
• Location filter. Drilling into a single location hides notes filed at a broader scope. A City-scoped Milwaukee note disappears the moment you filter to Keystone Lot, and returns when you clear that chip. (Verified.)

The practical consequence: scope a note at the level people will be looking when they need it. A note filed against one garage will not be seen by anyone reviewing the city as a whole, and a city note will not be seen by anyone drilled into a single site. If a note matters at both levels, it currently has to be written twice.

The filter chip beside the city selector (the sliders icon) shows a badge with the number of active filters, and opens a Filters drawer covering Dates, City and Location, with Clear all and Apply Filters. If a note you know exists isn't showing, check that badge first.

Also worth knowing: the forward month arrow is disabled at the current month. You can date a note in the future via the date picker, but you can't navigate the page forward to read it back.

Practical guidance

Write these:

• Causes for visible anomalies — events, closures, construction, competitor pricing, a rate change
• Things a chart can't show — a lost contract, a new neighbouring tenant, a staffing gap
• Corrections to the obvious reading — "the rain correlation here is coincidence; the drop was a gate outage"

Skip these:

• Restating the number. The dashboard already shows it.
• Speculation without a marker. If you're guessing, say you're guessing.
• Anything you wouldn't want a client reading. Treat notes as visible to everyone with portal access unless you have confirmed otherwise.

Conventions worth agreeing as a team, since the tool enforces none of them:

• Sign off with initials, since the card does not display an author
• Prefix ambiguous entries, e.g. [unconfirmed]
• Use Date range for multi-day events rather than filing three near-identical single-day notes

Internal notes — CS / account team

Points to be aware of before this goes to clients.

Confirmed behaviour

• 500-character hard cap. Long context has to be summarised or split.
• No author or timestamp is displayed on the card. Nothing in the UI attributes a note to a person — so a note's provenance is only whatever the author typed into the body.
• No search, no sort, no filter within the Notes panel, and no Positive/Negative filter. Discovery is entirely via the page's month and location filters.
• Note Type is Positive/Negative only. There is no neutral or informational option, which forces a judgement call on notes that are neither.
• Delete is a single confirmation with no undo.

The scope/filter interaction is the main support risk. Because a City-scoped note vanishes under a location filter, the most likely client complaint is "my note disappeared." It hasn't — it's out of scope for the current view. Lead with that when triaging.

Not verified in this walkthrough — check before asserting any of it to a client:

• Whether an Organization-scoped note surfaces across every city. The test account had only one city, so this is inference, not observation.
• Whether a Locations-scoped note appears when the page is filtered to that location (very likely, but untested).
• How a date-range note behaves when the range straddles two months — does it appear in both, or only the month of the start date?
• Whether notes are visible to all users in an organisation, or gated by role. Nothing in the UI indicates permissions either way.
• What happens at exactly 500 characters — whether input is blocked or the save is rejected.