Cross-Check Observed Work-in-Progress Against Rate Times Mean Flow Time — Free
An open-work count and a completion rate are not comparable until elapsed flow time supplies the missing unit. Put all three on a lane-level dial before explaining why a service backlog appears different from its normal operating model.
The proof surface
Dispatch-capacity tools count work a station can handle. This dial applies a restricted steady-flow accounting relationship to disjoint lanes, contrasting a measured snapshot with rate × mean flow time. It does not optimize staffing or predict a customer's wait.
InputDisjoint service lane | completions per day | mean flow time in days | observed open items; relative-model-gap review mark (%)
Rare deviceDispatch-capacity tools count work a station can handle. This dial applies a restricted steady-flow accounting relationship to disjoint lanes, contrasting a measured snapshot with rate × mean flow time. It does not optimize staffing or predict a customer's wait.
Output artifactDisjoint-lane observed count minus flow model with row-by-row context
Cost$0 local calculation · no card, paid key, subscription or signup · proposed filing price is not for sale
Sample, not your facts: Illustrative inputs: Repairs lane | 5 | 2.4 | 14; Documents lane | 9 | 1 | 8. Relative-model-gap review mark (%) = 20. Disjoint-lane observed count minus flow model: 1 items observed minus modeled. All records are invented.
Before using the flow-time dial
Little's-law-style accounting relates average work-in-progress, average throughput and mean time within one consistent system boundary under stable conditions. A single snapshot is not automatically the long-run average. Completions must be counted in the same item units as open work, and flow time must cover the entire same lane from entry to exit. Use calendar days or workdays consistently; the app does not convert between them. Lanes must be disjoint if their quantities are added. The review percentage measures abs(observed-model)/model, with zero-model cases explicitly labeled unavailable for that relative ratio. It is a discussion threshold, not proof of instability, inefficiency or a staffing requirement.
Why the flat version breaks
Using a median instead of a mean
The rate-times-flow relationship needs compatible averages. A median can differ substantially in a long-tailed service queue and produce a different work-in-progress product. Confirm the statistic from the source rather than relabeling a convenient typical turnaround as a mean.
Counting the same open item in two lanes
Adding overlapping lanes double-counts work-in-progress. If an item is included in both waiting-for-review and all-open-work, their sum is not a system total. Keep rows disjoint or run separate comparisons and avoid a pooled total that appears more comprehensive than its boundary actually allows.
Treating a snapshot gap as a staffing prescription
The observed snapshot may differ from a long-run average even when the service process is stable. The app has no arrival history, variability or staffing constraints. Use the flagged relationship to ask a measurement question; do not claim that a particular number of employees will fix the queue.
How to work the flow-time dial
Draw the service boundary first
Define what counts as one item, when it enters and when it leaves each lane. A document pending a customer's response may or may not be inside that boundary, but the same convention must apply to both flow time and open counts. Keep customer identifiers out of the aggregate lane labels.
Choose compatible averages and a snapshot
Use a positive observed completion rate per day, a non-negative mean flow time in the same day convention and a whole snapshot count. Note the measurement periods privately. A median flow time is not the mean required by this model, and a peak-hour completion rate is not interchangeable with a whole-period average.
Multiply units, then inspect signed gaps
Items/day multiplied by days produces modeled items. Subtract modeled items from the observed count for each lane. The dial counts rows beyond your relative review mark, while the row retains actual item quantities. The total gap adds only disjoint lanes' counts and should be read beside the individual differences so cancellation remains visible.
Investigate incompatible observations before acting
Ask the operations owner about arrival bursts, measurement windows, rework and lane boundaries. A discrepant snapshot can be informative without supporting a staffing decision. If conditions are changing rapidly, collect an appropriate time series or seek an operations analyst's review instead of treating the product as a queue forecast.
What the flow-time dial separates
Question
Before
Inspect this instead
Using a median instead of a mean
The rate-times-flow relationship needs compatible averages. A median can differ substantially in a long-tailed service queue and produce a different work-in-progress product. Confirm the statistic from the source rather than relabeling a convenient typical turnaround as a mean.
Choose compatible averages and a snapshot
Counting the same open item in two lanes
Adding overlapping lanes double-counts work-in-progress. If an item is included in both waiting-for-review and all-open-work, their sum is not a system total. Keep rows disjoint or run separate comparisons and avoid a pooled total that appears more comprehensive than its boundary actually allows.
Multiply units, then inspect signed gaps
Treating a snapshot gap as a staffing prescription
The observed snapshot may differ from a long-run average even when the service process is stable. The app has no arrival history, variability or staffing constraints. Use the flagged relationship to ask a measurement question; do not claim that a particular number of employees will fix the queue.
Investigate incompatible observations before acting
This flow-time dial replaces a manual count or calculation, not source verification or the responsible person’s review.
Run it on the samples, right here
FIRST-LOAD
HYPOTHESIS / PROTOTYPE — checkout unavailable. Calculation is local. A draft is saved automatically in this browser profile when storage is available; Reset to sample clears it. Optional Pro history stores only five summaries and has its own deletion control. State links encode your inputs and can remain in browser history, clipboard or recipients’ records; share only non-sensitive rows. Optional external AI formatting leaves this device. The required site analytics beacon reports page activity; shared URLs contain encoded inputs. Do not treat an encoded URL as private. The calculator has no input-collection endpoint.
Restricted operations-model arithmetic only, not a staffing recommendation or service guarantee. Ask the operations owner or a qualified operations analyst to confirm system boundaries, compatible averages and steady-flow assumptions before acting on a gap.
Data note: The flow-time dial processes Disjoint service lane | completions per day | mean flow time in days | observed open items locally. Starter/sample selection and Run compute in this tab; no input is sent by the calculator. A local draft may be saved; explicit state-link sharing or optional external AI formatting can disclose inputs. Use non-sensitive labels.
Go deeper: the companion app files the same reading as a meter band gauge
The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the flow-time dial reading, and holds your drafts on this device — one complete free app run; the proposed $4 one-time filing layer is not for sale.
The flow-time dial answer stays complete for free. The proposed $4 one-time filing layer adds row CSV, print and five local reading summaries, not hidden answers. Checkout is unavailable; the article demo remains unlimited.
Restricted operations-model arithmetic only, not a staffing recommendation or service guarantee. Ask the operations owner or a qualified operations analyst to confirm system boundaries, compatible averages and steady-flow assumptions before acting on a gap.
What this is built on
Method: Items/day multiplied by days produces modeled items. Subtract modeled items from the observed count for each lane. The dial counts rows beyond your relative review mark, while the row retains actual item quantities. The total gap adds only disjoint lanes' counts and should be read beside the individual differences so cancellation remains visible.
All sample records, dates, quantities and labels are invented. No outside policy, contract, rate, clock offset, measurement or accessibility standard is represented as verified.
Google’s official pricing documentation, fetched 2026-10-01, says AI Studio is free in available regions. Optional formatting may require a Google account; manual local entry requires none. Limits can change and free-tier content may be used to improve products. Do not send private records.
Before: an open count was compared with a daily rate without matching units. After: explicit flow time supplies a model and each lane keeps its signed disagreement.
Three worked readings, with different inputs
Sample A — typical inputs
Repairs lane | 5 | 2.4 | 14
Documents lane | 9 | 1 | 8
Setting: Relative-model-gap review mark (%) = 20. Expected summary: 1 items observed minus modeled.
Rate times mean flow time gives twelve modeled open repairs and nine modeled open documents. Observed counts are fourteen and eight, producing signed gaps of +2 and -1. The pooled count gap is +1 because observed total is 22 and model total is 21. The individual row workings remain necessary: opposite lane gaps can partly cancel, so the summary is not a verdict that both lanes match.
Sample B — changed plan
Returns lane | 4 | 3 | 22
Setting: Relative-model-gap review mark (%) = 20. Expected summary: 10 items observed minus modeled.
Four completions per day times three days of mean flow time predicts twelve average items in the lane under a stable-flow model. The observed snapshot is 22, ten above that model, a relative absolute gap of 83.333333%. The review mark flags this disagreement but does not identify its cause. A burst of arrivals, a different measurement window or an unstable queue can all invalidate the comparison.
Sample C — boundary convention
Documents check | 10 | 1.5 | 15
Setting: Relative-model-gap review mark (%) = 20. Expected summary: 0 items observed minus modeled.
The product is fifteen modeled items and the observed count is fifteen, giving a zero signed gap. Equality at one snapshot does not verify steady state or establish a service guarantee. The throughput and flow-time averages still need a compatible boundary and observation period; a neatly matching number can arise by coincidence.
Optional AI formatting, never the calculation
Manual entry completes this flow-time dial for free without signup. If available to you, the free AI Studio interface linked in the sources may format fictional or non-sensitive notes; external access may require an account. No API key or AI call is built into this tool. Free-tier content may be used to improve products. Review each cell and transcribe it to the labeled row schema; do not paste the JSON object into the row box.
Format only these fictional or non-sensitive notes for a flow-time dial. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string", "string"]}], "setting": "string"}. The columns are Disjoint service lane | completions per day | mean flow time in days | observed open items; the setting is Relative-model-gap review mark (%). Keep all supplied strings and quantities exactly; do not calculate, infer missing entries, invent dates or add advice. If any required value is missing, return an empty rows array and ask me for it separately. I will verify every cell against my source and manually transcribe rows using vertical bars before running the local calculator.
An AI response is not executed, fetched or trusted as a result. Missing values remain questions; the strict local parser checks the rows you actually enter.