Exhibit A — Measurement Schedule (sample)
Sample structure. Illustrative figures. Not an offer.
This is what a measurement schedule looks like, with one row filled in to show the level of detail. The figures are made up for illustration — they are not a client result. Actual metrics, baselines, targets, and fees are set per engagement in the signed agreement.
What's actually in the contract
When we say the metric is in the agreement, this is the thing we mean. Every value driver that carries fee gets one row on this schedule, attached to the statement of work. One row, one metric, no ambiguity about what counts as success.
We publish this because the structure isn't the hard part. Working out which of your numbers can carry fee, and what a realistic target is — that's the part that takes twenty-five years.
Sample structure. Illustrative figures. Not an offer.
- Metric
- Invoice processing cycle time
- Named precisely enough that neither side can argue later about what was being measured.
- Unit
- Minutes per invoice
- A rate, not a total — so it doesn't move just because your volume did.
- System of record
- NetSuite
- One system, agreed up front. Not a spreadsheet either party maintains.
- Extraction method
- Saved report "AP Cycle — S4 Baseline", monthly average
- The exact query. If we can't write down how the number gets pulled, the number can't carry fee.
- Baseline value
- 14.2
- Where you're starting. Captured before work begins — never reconstructed afterwards.
- Baseline captured
- 2026-08-04
- Dated, so the before-and-after is unarguable. This is the date that governs — see A.3.1 below.
- Baseline recorded
- 2026-08-06
- When the captured number was written down. Shown so you can see the gap between measuring and recording. Where the two dates match, the row says "same".
- Attested by
- J. Okafor, Controller — Schedule A-S1
- A named person on your side signed off that the starting number is right, on a countersigned baseline-capture schedule. Once attested, the baseline doesn't reopen.
- Basis
- Twelve-month average of posted AP invoices, excluding intercompany
- What the baseline number is an average of. Written down so the target is compared against like.
- Target value
- 4.0
- The number that decides whether the outcome fee is earned.
- Direction
- Decrease
- Stated explicitly, because "improve" is not a direction.
- Stabilization period
- 30 days from go-live
- New processes are messy for a few weeks. We don't measure during that, and neither should you.
- Measurement window
- 90 days
- Long enough to be real, short enough to settle.
- Cadence
- Monthly
- You see the number as it moves, not once at the end.
- Outcome fee allocated
- $3,400
- Our money, on this specific row. Each metric carries its own share, so a partial result pays out partially.
The fixed language that travels with the schedule
Four statements print under the table on every schedule. Three of them are fixed — word for word the same in every engagement. The allocation-basis line is the one that moves, because the allocation it describes is specific to your metrics; the wording below is the one we use by default. All four are reproduced here as they print, because the point of publishing the sample is that you can read the actual terms before you are in a negotiation about them.
A.3.1 Which Baseline date governs. Where a row states both a Baseline Captured date and a Baseline Recorded date, the Baseline Captured date governs — it is the date used for the condition precedent in SOW Section 6C.12(b), for the requirement that Baseline capture precede commencement of the Services, and for every other purpose of this Exhibit and the SOW. The Baseline Recorded date is disclosed so that Client can see the interval between measurement and recording; it determines nothing.
Allocation basis: Allocated pro rata to S4's estimated annual value for each Metric; any rounding residual is allocated to the largest-allocation Metric so the column sums exactly to the Outcome Fee.
A.3.3 Measurement Window and tolling — notice. The Measurement Window stated for a Metric is a duration in days, and that duration controls. Where the Window is tolled under Addendum Section 30.3, the duration is unchanged and the Window Close date shifts by the period of tolling. S4 will give Client written notice of the recalculated Window Close date within ten (10) business days after each tolling event, and a further such notice within ten (10) business days after the tolling ends. A Window Close date computed from the stated duration and any tolling notices given under this Section is the Window Close date for all purposes of this Exhibit.
A.3.4 Extraction Method — content. S4 represents that the Extraction Method stated for each Metric identifies only a query, report, saved view, or endpoint and the parameters required to reproduce the value, and contains no credential, secret, access token, or confidential identifier of either Party. If Client notifies S4 that an Extraction Method entry contains any such item, S4 will reissue the affected Exhibit A page with a conforming entry within five (5) business days; the reissue is a correction of form and does not alter the Metric, its Baseline, its Target, or its allocation.
How measurement runs
- › We measure, and hand you the underlying data with the result — not just the conclusion.
- › You get a defined review period to dispute it in writing. We recommend ten business days.
- › Each metric is scored met / not met on its own. No sliding scales in the early engagements — they invite an argument at the margin and they're hard to explain.
- › If you change systems or reporting mid-window, we go back to the dispute process rather than pretending the numbers are still comparable.
The real one is built for your systems
This sample uses invoice processing because it's easy to follow. Yours will use whatever your business actually runs on. Working out which numbers qualify is the first thing the diagnostic does.
Request a value diagnostic