Status, naming and governance

Decide whether a new KPI should be built at all.

Building a new KPI is three lessons of form-filling. Knowing you didn't need to is the part that actually saves time.

The query list carries Query title, KPI Name, KPI Id, Creator, Created, Updated and Status (Active, Draft, or Archived — 10.3 covers what archiving actually does), with a status filter and a search box above it, and two actions per row — delete and duplicate. It's entirely normal to see the same KPI Name more than once in this list — every row still carries its own unique KPI Id, which is what actually identifies it, so a shared name is never ambiguous in practice.

The duplicate icon copies a query in one click, no confirmation needed: it creates a new row titled "<original title> (1)", on Draft, with Assigned KPI cleared back to "Please select a KPI" — but the canvas itself, every component and operator in the formula, carries over exactly as it was. This is the fast way to start a new KPI from an existing formula as a template, without touching the original: duplicate it, then assign the new KPI and adjust the calculation from there.

The delete icon does confirm — a "Query deletion" dialog asks "Are you sure you want to delete this query?" with Cancel and Delete buttons, so there's no accidental one-click loss.

⭐ The real lesson isn't the mechanics of building a KPI — those are three lessons of straightforward form-filling. It's that a custom KPI propagates everywhere: dashboards, planning, driver trees, investor reports. Unlike a standard KPI, it can also be edited and deleted. That combination — wide reach, loose control — is exactly why the question worth asking before every new KPI is not "can I build this" but "should I, or does one already exist."

The Query Builder page, with a 2 Statuses filter, a search box, and Add new query and Add new KPI buttons above a table of queries listing Query title, KPI Name, KPI Id, Creator, Created, Updated and Status columns, every row showing Active status and delete and duplicate action icons. — 1Query title vs KPI Name — these can differ, and neither needs to be unique
2KPI Id — what actually identifies a row
3Status: Active, Draft, or Archived
4Delete and duplicate actions, per row
ValueWorks 2026.08

Takeaways

⚠ Caution
KPI Names can repeat across rows without any ambiguity — KPI Id is what actually identifies each one.
Duplicate copies the formula onto a new Draft row with no KPI assigned — a fast way to start a new KPI from an existing one as a template.
Delete asks for confirmation first — it's not a one-click loss.
A custom KPI reaches dashboards, planning, driver trees, and investor reports — and unlike a standard KPI, it can be edited or deleted.
⭐ The real question before building one: does an equivalent KPI already exist?

Surfaces covered

Status: Active / Draft
Query list (Query title, KPI Name, KPI Id, Creator, Created, Updated, Status)
Naming conventions
The duplicate trap
Who should be allowed to create KPIs

Micro-check

Two quick questions

Practice only — nothing here is scored or recorded.

1. What makes a custom KPI riskier than a standard one, specifically?

2. You want to build a new margin KPI that's very close to an existing one, and you'd rather not rebuild the formula from scratch. What's the fastest approach?

Previous Module quiz