Auctrix International co. · Business architecture

Value-stream mapping workspace

Trace one trigger to its customer outcome. Make work, information, waits, risks, evidence, and proposed changes visible in one practical exercise.

Printable worksheet

Educational planning guidance only. A completed map or estimate is not an audited or validated operating model. Your map, step details, assumptions, approvals, and notes are saved in this browser only. The optional learning pool is off until you opt in.

Opening this browser's worksheet…

01 · Current or proposed flow

Set the scope and record a baseline

Pick one value stream and define its start and end. Use observed values where available; leave missing values blank instead of guessing.

Value stream nameMap owner or roleMap confidenceTrigger — what starts the flow?Customer outcome and end conditionBoundary, inclusions, and exclusions

Baseline per completed outcome

These are user-provided measures, not Auctrix operating data. Include source, period, and any assumptions.

Cycle time (minutes)Cost per outcomeUse the same units in the pilot.User-defined risk score (1–5)Workforce hours per outcomeCost unitBaseline evidence sourceBaseline assumptions or gaps

Map version note

02 · Actors and handoffs

Map the work from step to step

Record each actor, inputs, output, next handoff, systems, waiting, measures, observations, assumptions, and opportunities. Add only the information categories needed for the exercise.

Map steps in sequence

Capture the work and information that move between roles. Unknowns are useful prompts.

Start with the first activity

Follow one trigger toward its customer outcome. Add a step when you are ready; no sample process data is prefilled.

Review prompts

Data exposure and threat review

0 flags from the details entered

No rule-based flags from the current entries. This is an educational prompt, not a security review or proof that a flow is safe.

Scenario lab · estimate

Compare a proposed change

Use your own baseline and evidence. Percent changes are user-entered assumptions; this calculator does not infer operating data or validate a business case.

Estimates are educational guidance. Enter the baseline source, assumptions, confidence, and evidence gaps for every scenario. Missing baseline values remain unknown.

New proposed change

Scenario nameConfidenceChange being proposedDescribe a change in general terms; do not add client or case details.Baseline or supporting evidenceSource, owner, and date; keep sensitive records out of the worksheet.AssumptionsEvidence gaps to close

Cycle-time reduction (%)Negative values model an increase.Cost reduction (%)Negative values model an increase.Risk-score changeLower scores mean less risk; scale is user-defined 1–5.Workforce change (%)Negative values mean fewer hours per outcome.

Dependency lab · estimate

Test a delay or unavailable dependency

Select the supplier, system, team, or approval step and estimate an interruption window. Downstream results follow the mapped sequence; recovery options remain prompts to validate locally.

Add at least one map step before modeling a dependency interruption.

Dependency scenario

Dependency typeEventSupplier, system, team, or approval nameFirst affected stepEstimated delay (hours)ConfidencePotential recovery optionSupporting evidenceAssumptionsEvidence gaps

03 · Privacy and security

Review every data movement

Each step has prompts for data type, roles, movement, retention, and safeguards. Rule-based flags surface threat scenarios and mitigation ideas; confirm them with the people responsible for security and privacy.

Never enter passwords, payment details, customer records, or unnecessary sensitive information. Use data categories, not individual values. Favor minimization, redaction, role-based access, audit history, and clear retention rules.

Minimize and redact

Map only the categories required to understand the flow. Remove identifiers from notes.

Limit access by role

Name the roles that need information and record any broad access or exceptions.

Set retention and audit

Record the deletion rule and how access, handoffs, or changes should be reviewed.

0 current risk prompts appear in the step editor.

Improvement plan · prompts

Turn mapped friction into testable actions

The ranking prioritizes data-protection flags, then recorded delays and scenario evidence. It is a planning aid, not an audited operating recommendation.

No improvement actions are defined yet

Add a mapped delay, a data-protection review flag, an improvement opportunity, or a proposed-change scenario to generate a prioritized plan.

Pilot and learn

Compare a small test with its estimate

Keep case-level records out of this tool. Record baseline and actual averages only, plus the pilot owner, scope, and a stop condition.

Do not enter passwords, payment details, customer records, or unnecessary sensitive information. Operational maps stay in this browser. Only an explicitly shared summary of averages from five or more completed cases reaches the learning endpoint.

Baseline dateBaseline source and periodPilot namePilot owner or accountable roleSmall pilot boundaryName the limited steps, cohort, or time window only.Stop conditionState the measurable safety or service condition that pauses the pilot.

Completed cases in this pilotA count only; never enter case records.Actual outcome date

Aggregated actual outcomes

Average cycle time (minutes)Average cost per outcomeUse the same units as the baseline.Average user-defined risk score (1–5)Average workforce hours per outcome

Ledger note

Decision evidence ledger

Keep the reasoning with each version

Map and scenario snapshots, source notes, assumptions, confidence, approvals, predictions, and pilot outcomes are stored locally with this browser's worksheet.

Reviewer or approving roleReview decisionApproval or review note

No decision versions recorded yet

Save a map version, scenario version, approval, or pilot outcome to start the ledger.

Optional · off by default

Cross-project learning

No map data is reused unless you opt in. Sharing needs sign-in and sends only the aggregate averages below from five or more completed cases. The shared pool is isolated to this Auctrix workspace and never includes names, project labels, step details, text, or account identifiers.

I explicitly opt in to sharing and viewing de-identified averages for this pilot. I understand this does not share my map or case-level data.

Cross-project learning is off. Your worksheet is not sent to the learning pool.