The Process Component™ Engine
Systemize your operations and build organizational traction. Speak your process once at the 20/80 level; our team handles the rest.
Secure Capture Scripts
Please enter your access code to view the guided recording scripts.
Capture Guides
EOS Core Process Capture Script
A guided conversation for capturing one Core Process at the EOS 20/80 level—simple enough to use, clear enough to approve, and ready to package.
Important: This is not the detailed procedure interview. Stay at the level of the major moves that drive the result. When detail is important for training or execution, identify the need and capture it separately with Script 02.
Before You Record
- Complete one recording for one Core Process.
- Use Accountability Chart seats or role titles—not individual names.
- Speak naturally. You do not need to read the question aloud.
- Aim for the handful of major steps, generally seven to fifteen—not every click, field, or subtask.
- If the Leadership Team has not agreed on something, say so. Do not guess.
A. Process Identity and Result
- Agreed Name: What is the agreed or working name of this Core Process? Use a simple company-wide name, such as Sales Process, HR Process, Accounting Process, or a specific Operations/Delivery Process.
- Seat Ownership: Which Accountability Chart seat owns this Core Process? Name the seat or role. If ownership is not yet agreed, state that clearly.
- Business Result: Why does this Core Process exist, and what business result should it reliably produce? Describe the outcome in plain language.
- Boundaries: What starts the Core Process, and where does it end? Define the trigger, first boundary, completion point, and final recipient or result.
- Applicability: When does this Core Process apply—and are there situations where it does not? Keep this high level; only note boundaries that materially change how the process is used.
B. The Major Steps—20/80 Level
- First Major Step: At the highest useful level, what is the first major step? Give the step a short action-oriented name, identify the role or seat that drives it, and briefly describe the result or handoff.
- Sequence of Steps: What is the next major step? Continue until the Core Process is complete. For each major step, provide: step name; one- or two-sentence description; primary seat/role; and the result, approval, or handoff that moves the process forward. Target seven to fifteen major steps.
- 20/80 Test: Looking at the full sequence, which details can be removed without changing the company’s essential way? Apply the 20/80 test. Keep what drives consistency and the desired result; move execution detail to supporting procedures.
C. Handoffs, Standards, and Measurables
- Cross-Functional Handoffs: Where are the most important cross-functional handoffs? Name the sending role, receiving role, and what must be complete or provided.
- Critical Standards: Which approvals, checks, or non-negotiable standards must remain visible in the Core Process? Include only the critical controls that protect the result.
- Service Expectations: Are there timing expectations, service standards, or deadlines that belong at the Core Process level? Do not add detailed task timing unless it materially affects the process outcome.
- Measurables: What Measurables show whether this process is being followed and producing the intended result? List existing Scorecard Measurables first. Label suggestions or unknowns instead of inventing them.
D. From Documented to Followed By All
- Audience: Which roles or seats must understand or perform part of this Core Process? This defines the training audience and helps package the material by role.
- Supporting Materials Needed: Which major steps require a supporting Operating Procedure, checklist, template, or screen/video demonstration? Only identify what is necessary for consistent execution or training; do not expand the Core Process itself.
- Common Misunderstandings: What do new employees or cross-trained employees most often misunderstand about this process? Capture the few explanations or warnings that should be emphasized in training.
- Training Ownership: Who will train the process, reinforce it, and address repeated deviations? Use seats or roles; note any decision still needed by leadership.
- Storage Location: Where should the approved process and its supporting materials live so employees can easily find them? Use the company’s existing environment whenever possible.
E. Agreement and Review
- Alignment Gaps: Where might leaders, departments, or employees describe the company’s way differently? Surface disagreements for review; do not reconcile them silently.
- Unresolved Issues: What is incomplete, uncertain, or still awaiting a Leadership Team decision? Create a clean clarification list.
- Ongoing Cadence: Which seat owns future review, and how often should this Core Process be verified? State the owner and preferred review cadence, if known.
Capture Complete When
- The process has a clear owner, purpose, start, end, and desired result.
- The major steps are simple, sequential, and at the 20/80 level.
- Critical handoffs, standards, and known Measurables are visible.
- Procedure and training needs are identified without being forced into the Core Process.
- Gaps and disagreements are explicitly flagged for Leadership Team review.
Independent support material; OpsBox is not affiliated with or endorsed by EOS Worldwide. EOS-related terms are trademarks of EOS Worldwide.
EOS Supporting Procedure and Training Capture Script
A guided conversation for capturing the practical ‘how’ beneath a Core Process—without adding unnecessary detail to the EOS 20/80 process document.
Use this script when: a major Core Process step requires repeatable instruction, judgment, exception handling, a checklist, or a demonstration for onboarding, cross-training, coaching, or retraining.
Before You Record
- Capture one procedure performed primarily by one role or seat.
- Identify the related Core Process and major step before describing the procedure.
- Use screen capture when the work is performed in software or the visual sequence matters.
- Explain the company’s current best way—not personal shortcuts or an ideal future state.
- If there are legitimate variations, decisions, or exceptions, describe them explicitly.
A. Procedure Identity and Training Audience
- Procedure Name: What is the name of this Operating Procedure? Use an action-oriented title that an employee would recognize in search.
- Core Process Connection: Which Core Process and major step does this procedure support? Name both so the process and procedure remain connected.
- Seat Ownership: Which seat or role performs the procedure, and who owns the knowledge? Use roles or seats—not individual names.
- Training Scope: Who needs to be trained on this procedure? Include primary performers, backups, cross-trained roles, reviewers, or managers who need visibility.
- Learning Outcome: What should a trained person be able to do correctly and independently when training is complete? State the observable learning outcome.
B. Trigger, Prerequisites, and Tools
- Trigger: What starts this procedure, and how does the performer know it is time to begin? Name the request, event, schedule, queue, or handoff.
- Prerequisites: What must be available or completed before starting? Include information, approvals, access, templates, files, equipment, or prior steps.
- Systems & Tools: Which systems, tools, forms, templates, or locations are used? Speak the exact name. If screen capture is not used, identify the path or link name clearly.
- Permissions & Safety: Are there permissions, safety requirements, or prerequisites a trainee must have? Call out anything that could block, delay, or create risk.
C. Exact Steps
- Step 1: What is Step 1? Describe the action, where it occurs, what information is used, and what successful completion of the step looks like.
- Subsequent Steps: Is there another step? Continue until the procedure is complete. For every step: state the action in order; explain important choices; identify the system or tool; describe the completion signal; and note the handoff when applicable.
- Critical Focus: Which steps are easiest to miss, misunderstand, or perform out of order? These become training emphasis and verification points.
D. Decisions, Exceptions, and Escalation
- Judgment Calls: Where must the performer make a decision or use judgment? Explain the rule, guideline, threshold, or experience-based consideration used.
- Common Variations: What common variations or exceptions change the normal steps? Describe the alternate path and when it applies.
- Troubleshooting: What can go wrong, and what should the performer do when it happens? Include corrections, retries, safeguards, and when to stop.
- Escalation Triggers: When should the performer ask for help or escalate—and to which seat or role? Use roles and clear escalation triggers.
E. Quality, Completion, and Handoff
- Quality Checks: What checks confirm the work was done correctly? Include quick self-checks, required review, reconciliation, approval, or evidence.
- Practical Standard: What does a good result look like? Describe the practical standard a trainee and coach can both recognize.
- Completion Signal: How does the performer know the entire procedure is complete? Name the final signal, status, record, output, or confirmation.
- Next Handoff: Who or what receives the completed work next? Describe the handoff, notification, required information, and timing.
F. Training and Reinforcement
- Context & Purpose: What should be explained before demonstrating the steps? Include purpose, business context, customer impact, and why the standard matters.
- Live Demonstration: What should the trainer demonstrate live or on screen? Identify the portions where seeing the work is more useful than reading it.
- Practice & Verification: What should the trainee practice, and how should a trainer verify readiness? Define a realistic practice task, observation, teach-back, or result check.
- New-Hire Coaching: What are the most common new-hire mistakes or misconceptions? Turn these into coaching points—not blame.
- Job Aids: What short reminders, checklist items, or job aids would help after training? Identify only aids that improve consistent use.
- Retraining Triggers: What changes, errors, or performance signals should trigger retraining? Connect updates and recurring breakdowns to reinforcement.
G. Ownership and Updates
- Approval Authority: Who approves this procedure and training material? Use the accountable seat or role.
- Change Notification: Who should be notified when it changes? Include performers, trainers, managers, and affected handoff roles.
- Verification Cadence: How often should this procedure be verified, and what events require an immediate update? Examples include system changes, process changes, recurring Issues, audit findings, or customer-impacting failures.
Capture Complete When
- A trained employee can understand when to use the procedure and what result is expected.
- The exact steps, decisions, exceptions, checks, completion signal, and handoff are captured.
- The procedure is explicitly linked to its Core Process and major step.
- The training audience, demonstration, practice, verification, reinforcement, and retraining needs are clear.
- Ownership, approval, and update responsibilities are assigned or flagged for decision.
Independent support material; OpsBox is not affiliated with or endorsed by EOS Worldwide. EOS-related terms are trademarks of EOS Worldwide.