Reports

A report says, for a closed period, what was done and what it changed. The agent writes the words; every number on it is read from your workspace for that period, so a report cannot claim more than the data shows.

​

Two formats

Both cover the last complete period: the ISO week, the calendar month or the calendar quarter. A board report is usually monthly.

​

Getting one

• In a chat. Ask for it, “the board report for last month”, or pick Report from the / menu first. A Report chat may read your data and publish the report, and nothing else that acts. See Modes.
• On a schedule. The weekly, monthly and quarterly report automations publish the client format. Say “board report” in an automation’s instruction to publish that format instead.
• By hand. Make one now under Results → Client reports publishes the client format for the period that ended last.

Board reports appear in the same list under Results → Client reports, beside their period and marked as board reports, for example Monthly board. In a chat, the published report opens in the work panel under Deliverable, drawn as the report itself, with its share link above it to copy. The agent’s reply says what the report is for and what to look at first; it does not retype the report’s numbers.

​

The board report

The board report reads in this order:

1. Summary. The totals in a sentence (how many goals stand at each pace below; how many pieces of work shipped; what was spent), and the agent’s highlights.
2. Goals. One row per goal that existed by the end of the period and is not archived: what it measures, where it stands now with its sample size, the target, the deadline, and its pace.
3. What shipped. Shipped, waiting and failed counts, and the shipped work by kind, for example “4 pull requests, 2 directory listings”.
4. Spend. What the workspace spent in the period, in US dollars.
5. Visibility. One line: named in X of N answers across every engine, how many days in the period were read, and how many changes a re-read proved to move.
6. Next period. What comes next.

​

Reading a goal’s pace

The pace is the goal’s own stored verdict, quoted as it stood at the end of the period. A goal on a business signal, such as sessions from Google Analytics, is marked (business signal): it is shown beside the work, not credited to it.

​

What the board report does not claim

• A section whose data could not be read says so: “The goals could not be read for this report”, “Spend could not be read for this report”. It is never shown as zero or left out.
• The agent’s words follow the same rules as every report: no movement words (increased, dropped, improved) unless a re-read proved the change, and counts written as “X of N answers” rather than percentages.
• Nothing on it promises an outcome. Attensira guarantees the volume of work, not visibility; the report shows the work and what was measured after it.

​

Sharing

Every report, client or board, gets a signed link at app.attensira.com/r/report/<token> that opens without an account, lasts 180 days and prints to PDF. Rotating the workspace’s receipt link revokes every link at once. The page carries your org’s branding. A report published from a chat is not emailed. Email delivery, recipients and the reporting standard work as described in Client reports.