Operational article · published
Baseline the Manual Workflow Before Automation
Measure current time, wait, rework, error, quality, cost, and escalation across a representative sample. Use this evidence-led ai workflows guide to build a reviewable manual.
Reviewed 2026-07-30 · National guidance, Austin proofThe task and the failure mode
Built for: Operators, product owners, and technical teams deciding whether a recurring business task is suitable for bounded AI assistance. This guide is for the person who must measure current time, wait, rework, error, quality, cost, and escalation across a representative sample. and leave a decision trail that implementation, editorial, analytics, or operations can review.
The difficult part of Baseline the Manual Workflow Before Automation is not producing another checklist. It is deciding which observation is strong enough to authorize a change. Without a baseline, speed claims and ROI estimates become anecdotes. Without a scoped manual workflow baseline, normal variation, reporting delay, and genuine defects can look identical. Preserve those distinctions before implementation begins.
Decision brief
Translate “done” into observable acceptance: another reviewer can reproduce the result, inspect the supporting source, and identify every unresolved exception.
For ai workflow discovery and scoping, keep completion, deployment, external processing, visibility, and business outcome as different milestones with different evidence.
If evidence conflicts, retain both observations and classify the likely reason. Do not average incompatible states into a clean but misleading result.
Questions to answer before changing the system
- 01Which cohort, date window, device, market, or environment definition must be fixed before comparison?
- 02What is deliberately outside the scope of this ai workflow discovery and scoping decision?
- 03What control case would reveal collateral damage from the proposed change?
- 04How will the implementation owner know that measure current time, wait, rework, error, quality, cost, and escalation across a representative sample. rather than merely completing a task is the goal?
- 05Which valuable path must remain unchanged while Baseline the Manual Workflow Before Automation is implemented?
Workflow
- 01Create the manual workflow baseline before collecting evidence so every observation has a destination, state label, and reviewer.
- 02Save timestamps, versions, filters, and requested-versus-final states in the manual workflow baseline; avoid relying on a screen remembered later.
- 03Stratify cases by route or workflow state, not by convenience, and document what the sample cannot represent.
- 04Attach a confidence boundary and exception disposition to each row in the manual workflow baseline.
- 05Convert the manual workflow baseline into a bounded implementation handoff with owner, dependencies, invariant, and stop condition.
- 06Validate the manual workflow baseline for completeness, broken links, malformed evidence, missing owners, and unresolved dispositions.
- 07Publish or hand off the manual workflow baseline only after its source links, dates, owners, and evidence-state labels are reviewable.
Evidence to retain
- The manual workflow baseline, headed with “Baseline the Manual Workflow Before Automation,” identifies the decision owner, reviewer, affected surface, explicit exclusions, and observation date.
- A direct before-state receipt for measure current time, wait, rework, error, quality, cost, and escalation across a representative sample.. Keep the requested and final state, timestamp, version or report definition, and the source that produced the observation.
- One cluster-specific proof item: output rubric and prohibited outcomes. Connect it to the case where it was observed and explain why that case represents this decision.
- One independent cross-check using pilot scope, stop conditions, and decision date. If the two observations disagree, preserve both and classify the likely boundary instead of selecting the cleaner result.
- A representative case set for Baseline the Manual Workflow Before Automation: ordinary, high-value, edge, failure, and unaffected control, each with an expected result written before the test.
- The primary-source trail behind Without a baseline, speed claims and ROI estimates become anecdotes. Record which part of the wording is directly supported and which part remains a project-specific inference.
- A disposition for every exception in the manual workflow baseline: fix, monitor, accept with rationale and expiry, escalate for qualified review, or remove from the admitted scope.
Worked decision: Baseline the Manual Workflow Before Automation
- Situation
- The current sample includes only the most visible success path.
- Question
- Measure current time, wait, rework, error, quality, cost, and escalation across a representative sample.
- Evidence
- Build the manual workflow baseline; include a representative case, an exception, a control, timestamps, and the cluster-specific observations listed in this guide.
- Decision
- Apply the smallest change supported by the evidence, assign every exception, and keep the broader ai workflow discovery and scoping surface unchanged until it is tested.
- Acceptance
- The reviewer can reproduce the observation, inspect the primary sources, verify the changed state, and identify what remains unmeasured.
Manual workflow baseline release checklist
- Material claims cite primary sources that support the exact wording used.
- A rollback, containment, or stop condition exists before release.
- Measures include source, calculation, window, cohort, exclusions, and coverage.
- Synthetic checks and test records are identified so they do not pollute operating reports.
- The working explanation “Without a baseline, speed claims and ROI estimates become anecdotes.” has at least one written disconfirming test.
- Related routes, records, components, or workflows are checked for inherited impact.
- The report states which broader tests were skipped and why the selected checks are sufficient.
- The final conclusion separates observation, inference, counterevidence, and unknowns.
- The current state is saved with route, version, filter, environment, or cohort context.
- Personal, sensitive, confidential, and secret values are excluded from browser analytics and shared artifacts.
What to measure—and what it does not prove
- Baseline the Manual Workflow Before Automation primary state: measure time and cost compared with the current baseline. The manual workflow baseline must name the source, calculation, route or cohort, observation window, and freshness.
- Quality control for measure current time, wait, rework, error, quality, cost, and escalation across a representative sample.: sample the records behind pilot expansion requiring a recorded evidence review. A clean rate does not establish that individual cases are complete, correctly classified, or free of duplicates.
- Exception measure: count unresolved, accepted, escalated, repeated, and timed-out cases created by this decision. Pair volume with an owner and response target instead of blending failures into the success denominator.
- Outcome boundary: review the downstream user or business result after the planned lag, but do not treat completion of manual workflow baseline as proof of ranking, revenue, compliance, safety, or causal impact.
Boundaries and caveats
Automation value depends on the full workflow, not model accuracy alone.
Baseline the Manual Workflow Before Automation supports a bounded decision, not a universal rule. Recheck cases whose route, market, device, provider, data sensitivity, or operating model differs from the admitted sample.
The manual workflow baseline can show what was observed and why an action was chosen; it cannot turn unavailable evidence or an external platform outcome into a confirmed result.
Primary documentation and business facts can change. Revalidate the sources and obtain qualified legal, privacy, security, medical, financial, or regulatory review when measure current time, wait, rework, error, quality, cost, and escalation across a representative sample. could create material harm.
Primary sources
- NIST: Artificial Intelligence Risk Management Frameworkwww.nist.gov
- NIST: Generative AI Profile for the AI Risk Management Frameworknvlpubs.nist.gov
- OpenAI API: Evaluation best practicesdevelopers.openai.com
- OpenAI API: Structured model outputsdevelopers.openai.com
Start with one bounded case
Start with one representative case and open a manual workflow baseline. If the evidence confirms the suspected mechanism, admit the smallest useful batch for implementation. If it does not, keep the finding as an unresolved hypothesis and return to the ai workflow discovery and scoping baseline instead of expanding the change.