Docs
How the numbers are computed: metrics & flags
Every number BoardMark works out — boards, sprints, Insights, releases, template flags, RICE, summaries and the bill — with its rule, who sees it and its limits.
How to read these numbers
Every number, state and flag on this page is worked out from the data on the board by fixed rules you can read — no AI decides them, so you get the same result every time. Most tables have four columns: Number · How it is measured · Who sees it · Limits (where “Who sees it” is missing, the section says it above the table).
- Flags are computed when the card is read, never stored, and never move a card for you — change a date or a field and the flag follows
- “Today” and “which day” use your company's time zone (Thailand time, Asia/Bangkok, for companies in Thailand); seats on the bill are counted at 00:00 Thailand time
- Working days are Monday to Friday with no public holidays removed; cycle time and lead time count calendar days, weekends included
- Status moves are recorded in full since 7 Oct 2026, so numbers that need older history may be incomplete
- AI agents read the same numbers over MCP as people see; they should report them as returned and never guess more
On the board
| Number | How it is measured | Who sees it | Limits |
|---|---|---|---|
| WIP and WIP limit | Cards in a column right now against the limit you set: over = warning colour ▲, at ●, within ✓ | Everyone in the project | A warning, never a block; On Hold is in the to-do category, so it does not count as WIP |
| Board throughput (Kanban, Delivery pipeline) | Cards now in a Done column, counted by the week of their last change (7-day weeks); the right bar is this week | Everyone in the project | Uses the last change, not the done date — a card edited after it was finished moves to the week of the edit; Insights has the exact numbers |
| Done cards on the board | Kanban and Delivery pipeline boards show this week's done cards (since Monday 00:00); older ones leave the board. With Releases on, done cards of a release shipped to production leave at once | Everyone in the project | Nothing is deleted — find them with ⌘K, on the release page and over MCP |
| Sub-tasks x/y | Children in a done-category column ÷ all children | Everyone in the project | One level of children only |
| Votes (Feedback / Idea box, or a project with votes on) | One vote per person; press again to take it back | Everyone in the project; viewers cannot vote | No vote weighting |
Sprints, burndown and velocity (Scrum)
| Number | How it is measured | Who sees it | Limits |
|---|---|---|---|
| Burndown | Story points of the sprint's cards not yet in a done-category column, recorded once a day; pick the sprint when parallel sprints are on | Everyone in the project; agents use get_burndown | Cards without points count 0; a column category change applies from that day (closed sprints keep their numbers); a Jira Cloud import brings a backdated burndown, a CSV import starts on the import date |
| Days left / overdue | Sprint end − today; a running sprint past its end shows a red “n days overdue” badge until someone completes it | Everyone in the project | Sprints never close by themselves |
| Sprint points and issue count | Points and cards in the sprint, and how many of them are done | Everyone in the project | Unfinished work at closing goes to the backlog, a new sprint or a planned sprint — the person closing picks |
| Velocity | Points finished in each of the last 3 closed sprints (in the Sprint review report) | Report recipients (Premium) | No weighted average and no forecast |
Insights (Premium)
Full definitions are in https://www.boardmark.ai/docs/insights; this table sums up the rules and the gaps. Ranges: 7 / 30 / 90 days, a quarter or custom (≤ 366 days), against the period of equal length right before. Project admins see per-person rows of their project, company admins every project, plain members team-level numbers only.
| Number | How it is measured | Limits |
|---|---|---|
| Cycle time (median, p85) | First entry into an in-progress-category status → latest entry into done, in calendar days | Cards that jumped straight to done, or moved before 7 Oct 2026, are left out — the page always says “measured n of m cards” |
| Lead time (median) | Card created → done, backlog waiting included | Always longer than cycle time |
| Throughput | Cards and points done per week = range total ÷ (days ÷ 7) | No points = 0 pts but still 1 card |
| Stuck work | An in-progress card with no status move for ≥ n working days (the project's stuck setting, 3 by default) | Editing text or commenting is not a move — only status moves count |
| Done per person | Cards and points done in the range, counted for the current assignee | Not always who moved or did the work; no per-person comparison with the previous period; not a performance score |
| Agent share of writes | Writes made through any AI agent ÷ all writes | Neutral, not good or bad |
| Bugs opened vs closed | Bugs created in the range against bugs done in the range | Only cards of type bug |
| Release cost / bugs after | Points and cards split feature / bug; bugs after = bugs created within 14 days after the production date | No money or labour cost; with overlapping releases a bug counts for the latest one shipped before it was created |
Release readiness
With Releases on (paid plans), the Releases tab decides each feature's state (an epic in the release; cards without an epic form an “other work” group) in this order — the first rule that matches wins:
| State | When |
|---|---|
| Blocked | Any of its cards (the epic too) is On Hold, or blocked by a card that is not done |
| At risk | An open critical or high bug, a card in Test Rejected, or a milestone date passed before its cards reached that stage |
| Ready | Every check passes: all cards dev done and passed every environment before production (Scrum / Kanban: all done), no open critical / high bug, nothing rejected, not blocked |
| On track | Everything else — moving, not complete yet |
- Release state: Not ready = a required gate item fails · Ready with risks = only optional items fail · Ready = all pass · Released
- Default gate — automatic: all features passed the last environment before production (Scrum / Kanban: all done) ✱, no open critical bug ✱, no blocked feature ✱, no open high bug; ticked by people: Release note ✱, Deployment package ✱, Rollback plan ✱, CAB approval, Security review (✱ = required) — release managers and admins add their own items
- Bugs count by the severity of open cards of type bug; a bug without a severity never makes a feature At risk
- On a Delivery pipeline, marking a release Released moves its cards in the last Passed column before production to Done; shipping with a failing required item needs a reason (kept in the audit log)
- Who sees what: everyone in the project (viewers too) sees feature states and the timeline; release managers (the Manage releases switch) and admins see each gate item and the scope history; members see the gate totals
Template flags
Flags come from a card's dates and fields every time it is read. Each flag is a list-view filter and a flag= value of search_issues; everyone in the project sees them. Values marked “adjustable” are set in Project settings.
| Flag | Template · on | Rule | Limits |
|---|---|---|---|
awaiting_signature | Sales & Billing · deal | In Sent for ≥ 7 days from sent_at (adjustable) | A Lost deal has no flags |
bill_due | Sales & Billing · installment | Not invoiced (no invoiced_at) and bill_on ≤ today | — |
due_soon | Sales & Billing · installment | Invoiced, not paid, due_on within 3 days (adjustable) | — |
overdue | Sales & Billing · installment | Invoiced, not paid, past due_on (shows n days) | Record paid_at yourself when the money arrives |
all_paid | Sales & Billing · deal | Every installment Paid and Σ paid_amount ≥ amount, but not Closed yet | Never closes the deal for you |
sla_soon / sla_over | Service desk · request | sla_due within 1 day / past sla_due; sla_due is set from the urgency when created: Urgent 1 · High 3 · Normal 7 · Low 14 days (adjustable) | No flag while Waiting or Done |
over_budget / spent_warn | Budget planning · budget line | actual > planned / actual ≥ 80% of planned (adjustable); remaining = planned − actual | Typed figures, not read from your accounts |
off_track / at_risk / on_track | Roadmap & Goals · goal | off_track = past end with progress < 100 · at_risk = elapsed % of start→end − progress % > 25 before end · on_track = the rest | None for a done goal or one without start / end |
Reminders: every morning at 08:00 (company time) BoardMark tells the deal's owner, watchers and assignee — bill_due on the morning of bill_on once, due_soon once, overdue the day after due_on and then every 7 days until paid, awaiting_signature and all_paid once; Service desk has its own SLA due switch; Budget planning rings the bell only; off_track rings the goal owner's bell once.
RICE, rollups, formulas and totals
| Number | How it is measured | Who sees it | Limits |
|---|---|---|---|
| score (RICE) | reach × impact × confidence ÷ effort, rounded to 1 decimal | Everyone in the project | Empty until all four are filled in, or when effort = 0 |
| progress (rollup) | Mean over the linked targets (relates, blocks, delivers), equal weight: a card in a done column = 100%, any other 0%; a release = % of its cards past the last gate (shipped = 100%) | Everyone in the project | A card in progress counts 0%, not halfway; one level deep; targets the reader cannot open are skipped, so people with different access may see different values |
| linked | Number of linked targets the reader can open | Everyone in the project | — |
| Delivery · N% (deal) | Rollup progress of the release or cards linked to the deal | Everyone in the project | Same rule as progress |
| formula | a − b, a + b or a / b of number / money fields on the same card, e.g. remaining | Everyone in the project | Read-only, never stored |
| Column and totals rows | Sales & Billing: each column header sums its deals; a deal shows paid / total and “n of N installments collected”; Budget planning: Σ planned / actual / remaining of the filtered rows | Everyone in the project | Money has 2 decimals in the project's currency; no currency conversion |
Automatic summaries (Premium)
| Number | How it is measured | Who sees it | Limits |
|---|---|---|---|
| Standup: period covered | Since the last standup; Monday covers since Friday | The recipients you set, only for projects they can open | No standup on a day with no change (you can turn the empty one on); lists only people who did something — there is no list of people who did not |
| Stuck work | An in-progress card with no status move for ≥ n working days (3 by default) | Recipients | Same rule as Insights |
| Overdue | Sales & Billing installments past due_on and Service desk requests past sla_due | Recipients | Other cards of the project are not included |
| Open bugs | Critical / high bugs not done | Recipients | Bugs without a severity are not counted |
| Project health (executive report) | The worst flag of the project's Roadmap & Goals goals; with no goals, the running sprint's progress against its dates by the same off / at risk / on track rule; neither = no value | Report recipients (company admins by default) | Kanban / pipeline projects without goals have no health value |
| Throughput in the executive report | Cards done in the period against the period of equal length before | Report recipients | No points |
The bill estimate and the invoice
| Number | How it is measured | Who sees it | Limits |
|---|---|---|---|
| Billable seats | Enabled seats counted daily at 00:00 with that day's plan: max(0, Σ seat-days − Σ free seat-days) ÷ days in month, rounded to 2 decimals, per plan; 2 free seats a day on Pro days (none on Premium) + a coupon's seats on the days it runs | Company admins | Suspended / deactivated seats and AI agents are never billed |
| Seat amount | Billable seats × the price per seat per month (Pro ฿249, Premium ฿329, excl. VAT) | Company admins | The day of a plan change counts at the higher plan |
| Storage | The month's peak above 10 GB, rounded up to 10 GB blocks at ฿70 each | Company admins | The peak, not the average |
| VAT and withholding | VAT 7% on the pre-VAT subtotal; a juristic company may withhold 1% (e-WHT) or 3% of the pre-VAT subtotal; amount due = total incl. VAT − withholding | Company admins | Companies outside Thailand pay in USD, 0% VAT, no withholding |
| This month's estimate | From the days counted so far, on the Admin console | Company admins | Not the final amount — the invoice comes on the 1st of next month, due in 15 days |
Four worked examples are in “How is my bill calculated? (examples)” in https://www.boardmark.ai/agents/pricing-faq.md and https://www.boardmark.ai/faq.
What BoardMark does not measure
- No ranking or performance score per person, and no person-against-person comparison
- No time tracking, and no money or labour cost in release cost
- No delivery-date forecast or Monte Carlo
- No public holidays removed and no team working calendar
- Numbers that need history before 7 Oct 2026 may be incomplete; cards imported from Jira Cloud bring their Jira status history