How does Fab measure throughput and first-pass success?
Throughput counts Issues whose latest move to done falls within the selected period and which remain done at the report cutoff. The Lifecycle no-reopen proxy is the share of those Issues with complete history that were never reopened. Fab reads these lifecycle records from Cortex.
Neither measure proves that the first result was accepted. A teammate can correct several candidates before closing an Issue once.
What counts as a reopen?
An Issue is reopened when it moves from done or canceled back to open or in progress. If it moves to done again, Fab uses the latest move to done as its endpoint. An Issue that is not done at the report cutoff is excluded.
Canceled work is excluded from throughput. About this data shows done and canceled counts separately. Closing an Issue records its status; it does not prove that someone accepted the work or that its checks passed.
An incomplete retained history leaves reopen history unknown and excludes that Issue from the proxy's denominator. If ten Issues are shipped, two have unknown histories and six of the remaining eight were never reopened, the no-reopen proxy is 75%.
What establishes first-pass success?
First-candidate acceptance needs the original requirements, the first artifact offered as ready or published, and evidence that it met those requirements without corrective work. Corrections after that candidate count as rework, even if the producer catches them before review or closure. Missing candidate or review evidence leaves acceptance unknown.
Open the dashboard options menu and select About this data to check counts, definitions, period and cutoff. Compare similar work over similar periods. Changes in Issue size or task mix can change the numbers without improving the work.