Weekly review

Reports in the navigation opens a screen headed Weekly Review: one line per KPI with its current value, its change over the last seven days and its status. It is a snapshot of the moment you open it, and it is built to be printed — the button at the top right hands the page to the macOS print dialog, which is also how you get a PDF out of it.

The screen

The navigation entry is called Reports, the page heading Weekly Review. Under the heading stands today’s date in long form, formatted in your app language: Saturday, July 25, 2026. At the top right sits the only button on the screen, Print / Save as PDF.

Below that comes a single card with one row per KPI. Every KPI in the app is listed — company-wide ones and project ones together, in one flat list, in the order the KPIs were created. There are no group headers, no project column, no filter, no sort and no search. If you organise your work in projects, that structure does not show up here.

While the data loads you see a placeholder: a title bar and one large grey panel. When you have no KPIs at all, the card is replaced by No KPIs yet — create some to generate a review. — with no button next to it. Create your first KPI on the Dashboard.

This screen only reads. It writes nothing, so it keeps working unchanged when the app is in read-only mode after an expired trial.

What a row shows

Each row is four columns, left to right:

Column	What it shows
Name and target	The KPI name, and underneath it Target: 50,000 EUR — the target formatted for your app language, followed by the unit.
Current value	The newest recorded value, formatted the same way, with the unit on its own line underneath it. An em dash (—) when the KPI has no value.
7-day change	The change against roughly seven days ago, printed with one decimal and an up or down arrow: +3.4%. A dash and — when it cannot be computed. Hovering shows the tooltip vs. 7 days ago.
Status	The status badge — On track, At risk or Off track. Replaced by the plain text No data when the KPI has no value.

Numbers use the grouping and decimals of your app language and unit, exactly as on the KPI cards: 50,000 in the English app, 50.000 in the German one. See Anatomy of a KPI for how the unit decides the number of decimals.

The status is the same one the Dashboard shows: the newest recorded value compared against today’s ideal line, with a 10 % amber band around it. It is graded against today, not against the day the value was recorded — so a KPI you stopped logging three weeks ago slides towards Off track here while its printed value stays the same. Ideal line & status explains the thresholds.

The 7-day change

This column is the only place on the page where a second point in time is involved. It works on the KPI’s loaded history — one point per calendar date that carries an entry, with the newest entry of a day winning.

How it is computed

1. The anchor is the newest recorded point, not today. If your last entry is from Monday, everything is measured from Monday.
2. From that point’s date, Pulsaria goes back exactly seven days.
3. It then takes the newest history point dated on or before that instant as the comparison value.
4. The percentage is (newest − comparison) ÷ |comparison| × 100, printed with one decimal. A change of zero or more gets a leading +. Unlike the value on its left, this percentage does not run through the app language’s number formatting: the decimal separator is always a point, +3.4%, even in the German app.

The colour follows the KPI’s direction, the arrow follows the raw number. For a higher-is-better KPI an increase is green with an up arrow. For a lower-is-better KPI a decrease is green — but with a down arrow, because the arrow only reports the sign of the change. Green means “this moved the right way”, not “this went up”.

When the column stays empty

You get the dash and — in three situations:

• The KPI has fewer than two recorded days.
• No recorded day is at least seven days older than the newest one. A KPI you started logging four days ago never fills this column, however many values it has.
• The KPI has no data at all.

Two things the number does not tell you

• How old the comparison is. Step 3 takes the newest point that is at least seven days old — if you skipped two weeks, that point can be much older than seven days, and the row still prints a plain percentage. Nothing is interpolated and the actual distance in days is not shown.
• A change from zero. If the comparison value is 0, a percentage change is undefined, so Pulsaria prints 0.0%. The arrow and colour still reflect the real movement, which is why a row can read +0.0% in green after going from 0 to 5.

The window is fixed at seven days. There is no 30-day or month-over-month column, and no way to change it.

When a row says “No data”

No data and the em dash mean the same thing: this KPI has no current value. Two causes:

• Nothing recorded yet, or nothing recorded recently enough. The app builds history from the 90 most recent dates that carry any entry, counted across all KPIs together. A KPI whose last entry is older than that window reads No data here even though the files are still on disk and still in the export.
• The KPI’s data could not be read — a corrupt or wrongly-shaped file, or a connector KPI whose connection is gone. On this page that looks identical to “never recorded”; the Dashboard is where you see the red card with the actual error message.

Rows with no data print the neutral No data instead of a red badge. That is deliberate: the Weekly Review does not accuse a KPI of being off track when it simply has no number. The KPI detail page is less forgiving and shows a red Off track badge in the same situation.

Printing and saving as PDF

Pulsaria has no PDF renderer of its own. The Print / Save as PDF button calls the system print function, and macOS does the rest:

1. Open Reports.
2. Click Print / Save as PDF at the top right. The standard macOS print dialog opens over the app.
3. To print, pick your printer and confirm. To get a file instead, open the PDF menu at the bottom of the dialog and choose Save as PDF, then pick a name and folder.

The file is written by macOS, not by Pulsaria — the app never sees it and does not remember that you made one.

What changes on the printed page

Pulsaria restyles itself for paper the moment the dialog opens:

• Colours switch to an ink-friendly light set regardless of your app theme: white page, dark grey text, darker cyan, emerald, amber and red for the accents. A dark-mode app prints as a light document.
• The sidebar and the bottom tab bar are dropped.
• The Print / Save as PDF button and the icon next to the heading are dropped.
• The glass panels flatten into plain white cards with a thin grey border; glows and shadows go away.
• The content area loses the margins it has on screen.
• One line appears that you never see on screen, at the bottom of the page: Generated by Pulsaria.

What stays is the heading, the date, and the KPI rows with their targets, values, changes and status.

What Pulsaria does not control

Paper size, orientation, margins, scaling and any page header or footer the system adds are all yours to set in the print dialog. Pulsaria defines no page rules of its own, and no page-break rules either — a list longer than one page breaks wherever it happens to land, which can be in the middle of a row.

The button on this screen is the app’s only print trigger: Pulsaria’s macOS menu bar has a Pulsaria, an Edit and a Window menu, but no File menu and no Print item.

What the Weekly Review does not do

Despite the name, nothing about it is weekly except the change column:

• No schedule, no email, no archive. Nothing is generated, sent or stored in the background, and past reviews are not kept — reopening the screen always rebuilds today’s snapshot.
• No date range picker. You cannot look at last month’s state or produce a review for a past week.
• No grouping, filtering, sorting or searching, and no per-project report.
• No charts. For a KPI’s curve, open its detail page.
• No file export button. JSON and CSV export live in App Settings — see Backup, export & moving Macs.