Monday.com

Monday.com exposes several object types through its API: boards, items, groups, users, updates, and workspaces. This integration focuses exclusively on items, which are the fundamental unit of work and the only object type that carries both assignee attribution and a measurable lifecycle. Boards and groups are structural containers rather than performance signals; updates record communication activity but carry too high a gaming risk to be reliable indicators. Five KPIs were retained from among twelve candidates, selected against three criteria: ability to attribute to an individual owner, resistance to gaming, and balance between leading indicators that enable intervention before deadlines are missed and lagging indicators that confirm actual delivery.

Delivery performance: reading volume, quality, and speed together

Three lagging indicators form the core of the delivery performance block. Items Completed counts the number of tasks an assignee brought to a done state during the period. On-Time Delivery Rate measures what fraction of those completed items were closed on or before their stated due date. Average Cycle Time measures how many days elapsed, on average, between item creation and completion.

These three indicators are designed to be read in combination because each one exposes a blind spot in the other two. A high Items Completed count says nothing about whether deadlines were respected or whether the work moved quickly or slowly through the queue. A high On-Time Delivery Rate, read alone, could mask a team that systematically closes low-complexity tasks on time while leaving the harder items to accumulate. Average Cycle Time, without reference to volume, cannot distinguish between a low-complexity board with inherently short tasks and a high-performing assignee who genuinely moves work through faster than peers. The three indicators together answer a question no single one of them can resolve: how much work was delivered, how reliably, and at what pace?

On-Time Delivery Rate also functions as the primary check on gaming of Items Completed. An assignee under pressure to close a high volume of items could theoretically rush completions regardless of quality. Because On-Time Delivery Rate penalizes any item that was marked done after its due date, a strategy of racing to close items without respecting deadlines produces a visible degradation in the rate. The two indicators are in tension in a structurally useful way: optimizing one at the expense of the other produces a pattern that a manager reading both simultaneously will immediately recognize.

Operational risk: leading indicators for daily intervention

Overdue Items counts all open items assigned to a user whose due date has already passed. Unlike the delivery performance block, which confirms outcomes after the fact, this indicator is actionable the day it changes: a manager reviewing the metric at the start of the day can immediately identify who is at risk, investigate whether the overdue state reflects a blocker, a capacity problem, or a prioritization issue, and intervene before the situation compounds. The gaming risk for this indicator is structurally low because the primary mechanism for artificial improvement — moving the due date forward — is visible to all board members and produces its own organizational signal.

Items Created measures the volume of items a user introduced into the system during the period, attributed to the creator rather than the assignee. It serves a different analytical function from the delivery indicators: it captures planning activity and contribution to project intake rather than execution output. A team member with a low Items Completed count but a high Items Created count is contributing primarily to scoping and planning rather than to delivery. The reverse pattern — high completion, low creation — characterizes an executor receiving work defined by others. Neither pattern is problematic in isolation; both become relevant when read against the role definition of the individual. Items Created is paired with Items Completed precisely to detect planning-without-delivery: a sustained gap between creation volume and completion volume per user indicates work entering the system faster than it is being resolved.

Scope and limits of the integration

Monday.com records status transitions and timestamps but does not measure the quality of work produced. An item marked done may represent a fully resolved deliverable or a partial completion that will require rework; the API data does not distinguish between the two. Status values are fully configurable per board, which means the definition of what constitutes a completed item varies across teams. This integration applies a standardized mapping, but teams that use non-standard status labels or that use the same board for workflows with structurally different cycles will produce indicators that are difficult to compare across contexts.

Due dates are optional in Monday.com and not universally used. When a significant proportion of items on a board have no due date, On-Time Delivery Rate and Overdue Items are calculated on a smaller subset of the actual workload, reducing their representativeness. The reliability of all five KPIs depends directly on the discipline with which teams assign items to individuals, set due dates, and update statuses in the tool: consistent practice produces indicators that support management decisions; inconsistent practice produces noise that cannot be distinguished from signal.