Your workspace, in perspective
The work, accounted for.
Follow the cost. Check what was accepted. Decide what to test next.
06 SEP 2026
Accepted outcomes
—Price coverage
—Project profit
UnavailableRevenue not linked.
Cost alone cannot establish profit.
01 / The resources
Where the cost belongs
02 / The result
Acceptance is the line.
A completed run is activity. An accepted outcome has a result, criteria and review evidence.
Synthetic acceptance records in the selected period. Counts describe this sample; they do not measure customer value.
03 / The project ledger
Put a name to the work.
| Project | Actual API charges | Accepted | Priced / eligible | Details |
|---|---|---|---|---|
| Selected total |
Accepted counts are outcomes, not sessions. Unassigned cost remains in workspace totals. Each cost column uses the selected basis only.
04 / A measured next step
A better run starts
with a better question.
Use a controlled comparison to test a workflow change. Keep the acceptance bar fixed and include the cost of review and rework.
Proposed experiment · no results yetDoes a tighter brief
reduce avoidable rework?
Harbor · Comparable interface tasks
ChangeBrief templateHold steadyAcceptance rubric