Completion rate
90%
STEADYWRK closes 90% of dispatched jobs successfully on a rolling 30-day window.
Basis: contractor outcome + payment disposition.
▸ Public Evals · v2.5.0
The evals we run in production — published.
STEADYWRK publishes eight operational evals on a rolling 30-day window: 90% completion rate, ±9% not-to-exceed (NTE) variance, a <2hr quote turnaround, 340ms median and 890ms p95 dispatch latency, and a 3% human override rate.
Every figure here is a canonical estimate, and the JSON says so in those words — "estimated": true and "source": "canonical_estimate". Contractor outcome and payment disposition is the basis each estimate is set against, not yet a live computation over closed jobs; when the sample supports computing them directly, the source field will change and so will this sentence. Nothing here is third-party audited. Every eval on this page has a matching field in the same public, no-auth endpoint — /api/dispatch/analytics/evals — which also reports its own provenance: estimated and goal_fulfillment.source say whether a figure came from production telemetry or from a canonical estimate, and this page repeats whichever the endpoint returns. No other dispatch platform publishes this.
Verify it yourself — no auth, no key200 · application/json
curl https://steadywrk.app/api/dispatch/analytics/evals?period=rolling_30d▸ Eval registry
Eight evals, one rolling 30-day window.
Each metric is defined, sourced, and dated below. Quote any single line — every statement stands on its own. All values are self-reported operational estimates, not third-party audited.
NTE variance
±9%
Final invoices land within ±9% of the not-to-exceed (NTE) figure STEADYWRK quotes at intake.
Basis: quoted NTE vs. settled invoice.
Quote turnaround
<2hr
STEADYWRK returns a not-to-exceed quote in under 2hr from work-order intake — a target, not a binding SLA.
Basis: intake timestamp vs. NTE-returned timestamp.
Dispatch latency (p50)
340ms
Median API latency from work-order accept to contractor notification is 340ms.
Basis: server-side request traces.
Dispatch latency (p95)
890ms
Tail (p95) latency for routing plus contractor outreach is 890ms.
Basis: server-side request traces.
Human override rate
3%
A human operator escalates or reverses 3% of agent decisions; everything below 70% confidence is routed to a person by design.
Basis: operator audit log.
Policy-violation catch rate
Tracking
Currently in tracking: gated by Zod schemas and a policy layer on every decision. STEADYWRK withholds a headline number until the sample size is large enough to publish honestly.
Basis: pending sufficient sample.
Cost per decision
Private
Kept private to preserve contractor-margin confidentiality. STEADYWRK publishes operational quality openly but does not expose unit economics that would leak partner pricing.
Basis: internal only.
▸ Live readout
Operational snapshot.
- Jobs dispatched (30d)
- Active production
- Active providers
- Contractor network in onboarding
- Data source
- canonical estimate
- Estimated
- yes — self-reported estimate
- Operating states
- Multi-state (on request)
- Headquarters
- Aqaba
▸ FAQ
Questions, answered.
- What evals does STEADYWRK publish?
- STEADYWRK publishes eight operational evals on a rolling 30-day window: completion rate (90%), NTE variance (±9%), quote turnaround (<2hr), dispatch latency p50 (340ms) and p95 (890ms), human override rate (3%), policy-violation catch rate (in tracking), and cost per decision (private). Contractor outcome plus payment disposition is the basis those figures are set against; the endpoint currently labels every one of them "estimated": true with "source": "canonical_estimate", and this page repeats whichever provenance the endpoint returns. Nothing here is third-party audited.
- How can I verify STEADYWRK eval numbers myself?
- Every eval on this page has a matching field in a public, no-auth, machine-readable endpoint: GET https://steadywrk.app/api/dispatch/analytics/evals?period=rolling_30d returns JSON. The page and the endpoint read the same canonical metrics registry, and the endpoint reports its own provenance — `estimated` and `goal_fulfillment.source` tell you whether a figure came from production telemetry or from a canonical estimate. Where the endpoint says `canonical_estimate`, this page says the same thing.
- What is the STEADYWRK dispatch latency?
- Median (p50) dispatch latency from work-order accept to contractor notification is 340ms; the p95 tail latency for routing plus contractor outreach is 890ms. Both are self-reported operational estimates, not third-party audited.
- How accurate are STEADYWRK quotes?
- Final invoices land within ±9% of the not-to-exceed figure STEADYWRK quotes at intake, and a quote is returned in under 2hr from work-order intake (a target, not a binding SLA).
- Does a human review agent decisions?
- Yes. A human operator escalates or reverses 3% of agent decisions, and every decision below 70% confidence is routed to a person by design.
▸ Embed this badge
Show the evals on your site.
A live badge that reads from the same canonical metrics as this page. The est. qualifier is rendered into the image. Paste the snippet anywhere:
<a href="https://steadywrk.app/evals">
<img src="https://steadywrk.app/api/evals/badge"
alt="STEADYWRK Dispatch Evals (est.) - rolling 30-day completion rate and average quote time"
width="280" height="44">
</a>