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

# Weekly scorecard

> Every Monday at 07:00 in your workspace's time zone: what shipped, what was named for the first time, which rivals lost a question, which receipts were verified, and what is next. Public link on by default, and never changed after it is made.

The **weekly scorecard** is one page about last week's work, made every Monday at **07:00 in your workspace's time zone** and emailed to you. It covers the last complete week, Monday to Sunday in that time zone, and it is written to be forwarded: to a manager, a client or a board.

## What it says

Five sections, always in this order:

| Section | What it lists | When there is nothing |
| - | - | - |
| **Shipped this week** | Each change that went live in the week, with where and the day it went live | "Nothing shipped this week." |
| **Named for the first time since we started reading** | Each [win](https://docs.attensira.com/agent/wins.md) detected in the week, in the win's own sentence | "This week no question was named for the first time since we started reading it." |
| **Rivals that lost a question** | Each question a rival was named on the week before while you were not, on which the same engine named you this week. For example: *On ChatGPT, the week before, rival.com was named on "best invoicing software for agencies" and you were not; this week the answer named you.* | "No rival lost a question to you this week." |
| **Receipts verified** | Each change whose [receipt](https://docs.attensira.com/measure/receipts.md) reached **Moved** in the week, and at which check | "No receipt was verified this week." |
| **Next week** | Approved work that has not shipped yet | "No approved work is waiting to start." |

A section that was read and found nothing says so in words. It never prints a `0`, which could mean "we did not look".

The scorecard says what was read, never what caused it. A rival losing a question is what the answers did; a verified receipt is **Moved** after the same [significance test](https://docs.attensira.com/proof/overview.md#when-is-a-change-real) every check uses, which is observed movement, not proof that the change did it. The scorecard never states money won and never says "because of our work".

## When a section cannot be read

Each section is read up to three times, with a short wait between tries. A section that still cannot be read is left out, and the scorecard says so in its place: "We could not read this section this week, so it is left out rather than shown as nothing." The rest of the scorecard still goes out on time. Nothing waits for a person to fix it by hand.

When many workspaces' scorecards come out short in the same week, that is treated as a fault on our side and we are alerted. One workspace's short week is not.

## It never changes

A week's scorecard is made once and stored as it was sent. Nothing read afterwards is added to it, so a link you forwarded in October shows the same words in December.

## The public link

Each scorecard has a public link from the moment it is made, and the email carries it. Anyone who opens it sees the scorecard without an account: your brand name and domain, the week, and the section text. It shows no ids and nothing else from your workspace.

* **On by default.** You do not have to publish anything to forward a scorecard.
* **Turning it off** stops every scorecard link the workspace has shared, at once. Turning it back on brings the same links back. Turning it on or off is a signed-in person's action (`PUT /v1/projects/{id}/scorecards/public-link` with `{"on": false}`); an API key or an MCP client cannot change it.
* **Rotating your workspace's receipt link** also stops every scorecard link, together with every other link the workspace shared. See [Sharing a receipt without an account](https://docs.attensira.com/account/receipt.md#sharing-a-receipt-without-an-account).

A link that is wrong, taken back or turned off shows nothing about the workspace.

The scorecard page has a **Download PDF** link, the same one a [client report](https://docs.attensira.com/agencies/client-reports.md#sharing) has: `/api/pdf/share/<token>` on the host the page is on, with no login. If the PDF cannot be made, the page opens your browser's print dialog instead.

## Who gets it

The scorecard is sent by email under the **Brief** category of your [notifications](https://docs.attensira.com/account/notifications.md): the switch or unsubscribe link that stops the morning brief stops the scorecard too. A scorecard is emailed once; a retry never sends a second copy.

## Over MCP and REST

* **REST:** `GET https://webapp.attensira.com/v1/scorecards` lists the scorecards newest week first (`limit` 1 to 52, 12 when omitted), and `GET /v1/scorecards/{week}` reads one by ISO week, for example `2026-W43`. Both take an API key with the `read` scope; on a key that covers more than one workspace, add `?project=`. A week with no scorecard is a `404`.
* **MCP:** `list` with `type: "scorecard"`, and `get` on `attensira://{workspace}/scorecard/{week}`.
* **Sharing:** [`POST /v1/shares`](https://docs.attensira.com/api/endpoints#post-/v1/shares) with `attensira://{workspace}/scorecard/{week}`, or the MCP `share` verb, returns the public link. It has no expiry. While the workspace's public scorecard links are off, it answers `409`.
* **Event:** the webhook `scorecard.ready` is sent once per workspace and week, when the scorecard is made. It carries `project_id`, `week`, `label`, `omitted` (the sections left out, usually empty), `share_url` (`null` while public links are off), `composed_at` and `uri`.

Each scorecard is:

| Field | What it is |
| - | - |
| `week`, `label` | The ISO week, and the week in words |
| `period_start`, `period_end` | The Monday it covers from, and the Monday after |
| `brand` | `name` and `domain` |
| `sections` | In the order above, each with `key` (`shipped`, `turned_green`, `rivals`, `receipts`, `next`), `title`, `lines` (each with its `text`) and `empty`, the sentence used when the section was read and found nothing |
| `omitted` | The sections that could not be read this week |
| `subject`, `body` | The email's subject and its text |
| `composed_at` | When it was made |
| `public_link`, `share_url` | Whether public links are on, and this scorecard's link |

Reading scorecards costs no credits, and stays possible when your credits have run out.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.