The commercial scope remains fixed. Measurement evidence must remain bound to the exact buyer-confirmed workflow and cannot be inferred from the public synthetic example.
Delivery is not measured value.
The USD 3,000 / five-business-day BUILD Workflow Exception Diagnostic can define a baseline and measurement method, but completed work alone cannot establish observed customer value. A bounded measured-value statement requires external evidence from the same workflow, denominator, observation window and buyer-approved sources.
This public template represents no customer state. The existing workflow-value example is synthetic arithmetic only; it cannot prove delivery, observed value, savings, ROI, customer outcomes or renewal/expansion evidence.
One recurring exception workflow · USD 3,000 · five business days.
Eight external-evidence conditions are required before measured value can be stated.
Buyer-confirmed baseline frozen for the same workflow definition and denominator
Delivery completion evidence for the agreed workflow scope and deliverables
Defined post-delivery observation window with start/end and sufficient data coverage
Observed comparison uses the same workflow definition, denominator and measurement rules
Observed metric values come from buyer-approved source evidence rather than synthetic inputs
Material workflow, volume, staffing, environment and process changes are recorded
Named buyer owner/reviewer accepts the bounded measured-value statement and limitations
Any customer-result or ROI statement is traceable to verified external evidence and explicit approval
No delivery or measurement state is represented.
delivery_started=false · delivery_completed=false · measurement_window_closed=false · measured_value_observed=false · customer_case_evidence=false.
Synthetic arithmetic cannot substitute for measured value.
The public workflow-value example demonstrates calculation structure only. Any measured-value, customer-result or ROI statement requires real external evidence and explicit buyer acceptance.