How to Measure IDP ROI in Outcomes, Not Pages

A monthly report can show thousands of pages processed and still leave the main question unanswered. Did the invoices get approved? Did the claims get completed? Did the applications reach a decision, with the result filed where the team can find it?
Pages are an input. An outcome is what got done with it — a completed unit of work, from the document arriving to the result being approved, delivered, and filed. If you buy document processing by the page, you will measure it by the page, and you will learn about volume and very little about whether work got done. Measuring IDP ROI in outcomes changes the questions, the baseline, and the way you read the invoice.
Start by defining a completed outcome
Before any measure makes sense, define what one completed outcome is for each type of work. For an invoice, it might be matched, approved, and filed with its data in the system of record. For another document, it might be reviewed, decided, and filed in the repository with an audit trail. The definition must be specific enough that two people counting the same work get the same number.
That definition is also the unit for every measure that follows. In Outcome Cloud™, work runs end to end: IDP Outcomes™ reads and extracts, Outcome Workflows™ routes approvals, and Outcome Repository™ files the result, and work is counted in Outcomes.
The outcome-level measures
Cost per completed outcome
Divide the total cost of the work for a period by the number of outcomes completed in that period. Total cost should include the platform cost and the internal review and handling effort that remains, so the measure reflects the whole job. Suppose a team processes invoices in a month: dividing its combined platform and review cost by completed, approved invoices gives a cost that can be compared from period to period. What matters is a consistent definition, applied the same way each time.
Exception rate and exception aging
The exception rate is the share of outcomes that leave the straight-through path for a missing item, a mismatch, or another issue that needs attention. Exception aging tracks how long those items wait before they are resolved and the work is completed. Read together, the two measures show both how often work is interrupted and how long the interruption lasts.
Cycle time from arrival to completed outcome
Cycle time starts when a document arrives and ends when the outcome is completed — not when extraction finishes. That end point matters, because work can move quickly through reading and then wait for review, approval, or filing. Measuring to completion shows where time actually accumulates.
First-pass completion rate
This is the share of outcomes completed without an exception, a correction, or a return for more information. It reflects how cleanly work moves from arrival to done in one pass. Track it by document type, because different types arrive with different levels of completeness and complexity. A change in this rate points you toward the documents, data, or steps that need attention.
Review effort per outcome
Review effort is the human time spent checking, correcting, and approving work, divided by the outcomes completed. It makes visible the work that page counts hide: a document can be counted as processed while a person still spends considerable time finishing it. Track it separately for routine items and exceptions. That split shows where effort concentrates.
Rework
Rework is work that must be done again after it was thought to be complete — a filing corrected, a match redone, or a result returned because something was missed. Count reworked outcomes and note the reason for each one. Rework is easy to overlook in page reporting because the pages were processed the first time; at outcome level, it shows up as extra cost and extra time.
Baseline before the project
A return cannot be shown without a starting point. Before a project begins, measure the same outcome-level numbers for the current way of working over a representative period. Use the same definition of a completed outcome, the same document types, and the same cost elements you plan to use later.
- Count completed outcomes, not documents received or pages handled.
- Record total cost, including internal review, correction, and filing effort.
- Note exception rate and aging, cycle time, first-pass completion, review effort, and rework.
- Keep the period and mix visible, so a later comparison reflects a similar kind of work.
The baseline does not need to be elaborate. It needs to be honest, consistent, and recorded before the new way of working starts, so no one has to reconstruct it from memory afterward.
Read the numbers after
After go-live, read the same measures over a comparable period and with a comparable mix of work. Compare cost per completed outcome first, then look at the measures that explain it: exceptions and their aging, cycle time, first-pass completion, review effort, and rework. If cost per outcome changes, those supporting measures should show where the change came from.
Read trends, not single moments. Volume, document mix, and difficulty vary from period to period, so a fair reading looks at movement over time and checks whether the underlying mix has changed. When cycle time falls, check that first-pass completion and rework have not moved in the other direction. The measures work as a set.
Connect pricing to measurement
Pricing mechanics determine how much of this picture appears on the invoice itself. Per-page pricing counts pages, so the invoice reports volume. Per-seat pricing counts access, so the invoice reports how many people can use the system. When work is priced per completed outcome, the invoice counts completed units of work — the same unit used for cost per completed outcome and the other measures above.
That alignment is the practical point. The number you pay on and the number you measure ROI on are the same, so the invoice itself becomes a starting point for an ROI report rather than a separate record to reconcile. Capacity fits the same picture: with SI Capacity, adding capacity is always the client’s choice, and there are no unexpected overage bills, so a change in volume does not rewrite the economics without a decision. For the pricing mechanics behind this, see our article on outcome-based pricing for IDP.
A framework you can keep using
IDP ROI is not a single calculation performed once. It is a small set of outcome-level measures, baselined before a project, read consistently afterward, and tied to a pricing unit that counts completed work. Start with the definition of done, keep the measures together, and let each reporting period answer the question page counts cannot: what got done, what it cost per completed outcome, and where the remaining time and effort go.
To apply this framework to your own work, talk with MaxxLogix about defining a completed outcome for your documents and baselining it before you change anything. You can also review how SI Capacity supports that approach in MaxxLogix SI™, so measurement and pricing stay on the same unit from the start.
Business Outcomes. Delivered.
