Weave Monthly Summary — What Weave Did This Month
Description
Section titled “Description”The monthly summary counts what Weave did in a project in one month: the problems it found when workflows finished running, the problems a later check no longer found, the changes it made that someone approved, and the problems marked as expected. Every number is a count of entries in the project’s Weave activity history, and you can open the entries behind each one.
Workspace administrators also have a workspace summary with the same counts for every project.
No AI is involved. The only estimate is the time saved, which says it’s an estimate and how it’s worked out. A month with nothing to report says so.
Open the Monthly Summary
Section titled “Open the Monthly Summary”- Open the project, select the Weave tab, and select Monitor in it.
- Click Monthly summary in the rail.
- Choose a month. The list starts with the current month, shown as, for example, October 2026 so far, followed by the eleven months before it.
Whose figures switches between For the project and For you: what Weave did for everyone in the project, or for you alone. For you leaves out the problems found and no longer found.
Refresh at the top of the page reads the summary again. Monthly summary appears for anyone whose role can read the project’s steps, workflows and tables, as Activity does. Months are calendar months in UTC.
What Each Number Counts
Section titled “What Each Number Counts”Each number has a sentence beside it saying what it counts. The summary shows only the number and its sentence; the names in the first column below are for this page.
| Number | Sentence |
|---|---|
| Problems found | Weave found 7 problems when workflows finished running. Each counts once, however often it was found. |
| No longer found | A later check no longer found 5 problems this month, including any first found in an earlier month. |
| No longer found after a Weave change | Of those, 2 were no longer found after a change Weave made, with approval, to the step, table or workflow they were about (for a workflow, to any of its steps). This shows the order of events, not that the change fixed the problem. Median time from Weave finding the problem, or finding it again if it had gone away, to the check that no longer found it: 26 hours, across 2 problems. |
| Changes made | Weave made 3 changes that someone approved. 1 of them has since been undone. |
| Marked as expected | 1 problem was marked as expected. It isn’t fixed: Weave stops reporting it as a problem. |
| Failed runs fixed | Weave fixed 4 failed runs, each confirmed by a re-run. |
| Answers reused | Teammates opened pinned answers 9 times. |
| Where this month’s problems stand now | Of the 7 problems found this month: 3 no longer found, 1 marked as expected, 3 still open. |
No longer found after a Weave change appears only when a later check no longer found at least one problem that month. Where this month’s problems stand now appears only when Weave found at least one problem that month.
Click Show 3 Entries (Show Entry when there is one) under a number to list the activity history entries it counts, with when each was recorded, and Hide Entries to fold them away. A number with no entries behind it has no button. For where this month’s problems stand now, the entries are grouped under No longer found, Marked as expected and Still open, each with its count. Under Answers reused, Show answer lists each pinned answer with how often it was opened and when last, never who opened it.
Time Saved
Section titled “Time Saved”Above the numbers, a line sums up the month, such as Weave fixed 4 failed runs, each confirmed by a re-run. Teammates opened pinned answers 9 times. That saved about 2 hours 45 minutes. Under it, the estimate says what it assumes: 30 minutes for each failed run fixed, and 5 minutes for each time a teammate opened a pinned answer.
- Answers reused counts only opens by someone other than the person who pinned the answer. In For you, it counts the opens of answers you pinned.
- Once a month, the first time you open the Weave dock in a project, it tells you about how much time Weave saved you there last month, with See how, which opens this page on For you. It isn’t shown when there’s nothing to count.
How the Numbers Are Worked Out
Section titled “How the Numbers Are Worked Out”- Problems found counts each problem Weave raised that month, once, and lists the first time it was raised. Weave raises a problem when it first finds it, not on every run that finds it again, so a problem still open from an earlier month isn’t counted, and one that goes away and comes back within the month is counted once.
- No longer found counts each problem a later check no longer found during the month, including problems first found in an earlier month. “No longer found” doesn’t mean fixed: the data may have changed so that the problem no longer shows. See What It Records.
- No longer found after a Weave change counts the problems in No longer found where, between Weave finding the problem and the check that no longer found it, Weave made an approved change to the step or table the problem was about, or, for a problem about a workflow, to any step in that workflow, and that change wasn’t undone before the check. The change may have been made for another reason, and it can be any approved action, such as re-running the step: this describes the order of events only. The median time runs from when Weave found the problem, even in an earlier month, to the check that no longer found it. For a problem that had gone away before and came back, it runs from when Weave found it again.
- Changes made counts every action Weave carried out with someone’s approval in the AI assistant — a step fix, the re-run that follows it, a new workflow, a table copy and so on — not only edits to existing settings. Undoing a change isn’t counted as a change of its own; the sentence says how many of the month’s changes have been undone since, at any time up to now. Changes you make yourself, and those made by an AI assistant connected over MCP, aren’t recorded, so they aren’t counted.
- Marked as expected counts each problem someone marked as expected during the month. See Mark a Finding as Expected.
- Where this month’s problems stand now takes the problems found that month, including any that went away in an earlier month and came back, and says where each stands today. A problem that is no longer found is counted there even if it was also marked as expected; a problem marked as expected and then no longer expected counts as still open. Only a check run as one of the project’s Architects closes a problem, so a problem fixed since a run by anyone else can still show as open; see Findings Are Recorded When a Run Ends.
What Isn’t Counted
Section titled “What Isn’t Counted”The summary counts only what the activity history records: problems found when a workflow finishes running, and changes made through Weave. It doesn’t count problems caught before a report read the data, or drafts and defaults you accepted. Problems Weave finds only between runs, such as a table not written on schedule, aren’t recorded in the history and so aren’t counted, and neither is a run Weave doesn’t check; see What the History Doesn’t Record.
A Month With Nothing to Report
Section titled “A Month With Nothing to Report”When there’s nothing to count for the month, the summary says so instead of showing zeros, for example There’s nothing to count for “Cost Model” in September 2026. An undo on its own, or a comment on a finding, isn’t counted.
What You See Depends on Your Access
Section titled “What You See Depends on Your Access”An entry about a step, table or workflow your role can’t open, or one that no longer exists, isn’t counted in any number, and a note says how many entries were left out. Where row-level security limits the rows you can read in the project, the summary also leaves out what Weave noticed from the size and contents of tables, and says so.
The Workspace Summary
Section titled “The Workspace Summary”Workspace administrators can see every project’s numbers on one page.
- Click the Weave button in the Weave dock’s header.
- Choose Workspace Summary… near the end of its menu.
- Choose a month, as in a project’s summary.
The window lists each project with activity that month, with Problems found, No longer found, No longer found after a Weave change, Changes made, Marked as expected, Failed runs fixed and Estimated time saved, and an All projects row with the totals. It shows counts only. Click a project’s name to open that project’s own summary for the same month, with the entries behind each number; that needs access to the project. A project that has since been deleted is listed as A project that no longer exists and opens nothing.
The workspace counts include every entry in each project’s history. A project’s own summary leaves out what its reader can’t open, so it can show lower numbers than the workspace summary does.
Workspace Summary… appears only for workspace administrators. Anyone else who asks for the workspace summary through the API is told Only workspace administrators can see the workspace summary. Each project’s own summary is on its Weave tab.
Through the API
Section titled “Through the API”GET /rest/v1/analyze/weave/monthly returns a project’s summary, with
project_id and an optional month in the form YYYY-MM (the current month if
left out). GET /rest/v1/analyze/weave/monthly/workspace returns the workspace
summary, with the same optional month. A month in the wrong form, or one that
hasn’t started, is refused.
Usefulness
Section titled “Usefulness”The Usefulness section shows how much of what Weave told you was worth reading, from the ratings people gave findings, with the number rated up and down, and how many answers Weave gave in place without calling an AI model. It counts only what you can open. Workspace administrators also see the figure for each rule and each project. If the figures can’t be read, the page says so and doesn’t claim Weave helped.