Quick orientation, so we start from the same page

• Tell me about your role and the specific warehouse or zone you want us to evaluate
• How many total associates work the shifts in that location on a typical weekday? Options: Fewer than 25, 25–50, 51–100, 101–250, More than 250
• Which three metrics your team reviews daily to judge throughput and labor performance? Options: Picks per shift, Units per labor hour, Orders per hour, On time shipments, Labor cost per unit, Shrink or accuracy, Other
• Describe the last time leadership asked you why labor cost per unit rose, what evidence did you have to answer?
• Which WMS category or family does your operation use for work assignment and tracking? Options: Legacy on-prem WMS, Modern cloud WMS, In-house custom WMS, WMS module of broader ERP, No structured WMS for assignment

Where the reporting leaves you blind

• What single reporting gap, if fixed, would immediately change how you staff and schedule a shift? Options: No per-associate productivity view, No task-specific achievable standard, Delayed reporting beyond the shift, Inability to link work assignments to measured activity, Other
• Walk me through a recent shift where aggregate metrics looked fine but you suspected hidden unproductive time, what did you notice and when did you first see it?
• How often do your reports allow you to separate task mix changes from genuine performance decline? Options: Always, Often, Sometimes, Rarely, Never
• Which specific downstream decisions break when you cannot see individual performance against an achievable standard? Options: Overstaffing or understaffing, Inaccurate incentives, Faulty labor forecasts, Poor supervisor coaching focus, Wrong hiring or retention choices
• If your current reporting had to remain as-is, what measurable business outcome would force you to revisit that decision within 90 days? Options: Labor cost per unit increases by >10%, Throughput drops below SLA, Turnover rises >5 points, Customer service impact, Regulatory or union complaint

When a shift misses its number, what really happens

• Walk me through the last time you missed throughput targets and had to explain it to senior ops or finance, what evidence did you bring and where did it fall short?
• Who inside your organization typically owns the post-shift root cause conversation, and who is often missing from that discussion? Options: DC Director, Operations Manager, Continuous Improvement lead, HR/People lead, WMS/IT lead
• How long does it take from noticing a productivity drop to implementing a corrective action, and what usually causes delays? Options: Same shift, Within 24 hours, 1–7 days, More than 7 days
• Describe one recurring, practical consequence you see when you cannot explain lower throughput, such as forced overtime, misallocated headcount, or missed customer windows
• Which single people or process failure would kill your confidence in a measured pilot before it completes? Options: Missing WMS mapping, No named data owner, Supervisor refusal to use dashboard, Union protest, Inaccurate time studies

If this worked well, what would change next quarter

• If a 15% measured productivity gain during a 60 day pilot matched your expectations, what would stop you from moving to production that week?
• Which three business outcomes would you expect to show improvement first if standards and real-time visibility were established? Options: Units per labor hour, Labor cost per unit, Supervisor coaching time, Order accuracy, Overtime hours, Retention of experienced associates
• How important is associate sentiment to your deployment decision, and what survey result would be required to proceed with incentives enabled? Options: Critical, >80% positive, Important, >65% positive, Considered but not decisive, Not a primary factor
• Describe the single operational threshold or KPI that, if consistently met during the pilot, would trigger executive approval to expand
• Who in your leadership chain would need to sign off to start a pilot immediately if those thresholds were met? Options: DC Director, SVP Operations, VP HR, Head of Continuous Improvement, Finance

What could derail this project before it starts

• Which integration dependency, if missing, would prevent the pilot from starting on schedule? Options: Real-time WMS API access, Work assignment feed, Time clock mapping, User account provisioning, None of the above
• How clean and accessible is the historical task and time data we would need to validate baselines, and who maintains that data? Options: Clean and accessible, owned by IT, Partially clean, mixed owners, Sparse or inconsistent, CI owns it, No usable historical data
• How many dedicated IT or integration hours can you commit during a 60 day pilot? Options: 0–20 hours, 21–80 hours, 81–160 hours, More than 160 hours
• Are there legal, union, or compliance approvals that must be obtained before any individual-level performance measurement is run, and who signs those approvals? Options: Yes, union approval required, Yes, internal legal signoff required, Both union and legal, No formal approvals needed
• If any of those constraints cannot be resolved within 4 weeks of project start, would you still run a scaled pilot? Options: Yes, with reduced scope, Yes, but delayed, No, wait until resolved

People, communication, and what adoption will look like day to day

• Who will be the first frontline users of the dashboard and who will coach supervisors on using it? Options: Supervisors, Team leads, Continuous Improvement coaches, Operations managers, Other
• Which supervisor capacity limits would stop them from running purposeful coaching conversations during the pilot? Options: Span of control >25 associates, No scheduled coaching time, Too many systems to check, Insufficient training budget, None of the above
• Tell me about prior change efforts that affected morale, what made them land poorly and what helped them land well
• Does your collective bargaining agreement or site leadership expect a formal consultation before implementing performance measurement, and how long does that process take historically? Options: Yes, typically 2–4 weeks, Yes, typically 1–3 months, No formal consultation required, Depends on the issue
• If supervisors refused to participate or coach during the pilot, what immediate action would you take and who would make that call?

Pilot scope, acceptance gates, and measurement details

• Which pilot boundary would give you meaningful confidence in scaling, zone size or task variety: a single high-volume zone, cross-zone sample, or role-based sample? Options: Single high-volume zone, Cross-zone sample, Role-based sample of core tasks, Other
• List the core modules you consider mission critical for the pilot to demonstrate value Options: Time studies and engineered standards, Real-time supervisor dashboard, WMS integration for assignments, Incentive calculation engine, Retention and HR reporting, None of the above
• What acceptance criteria would make you call the pilot a success and move to rollout, specify metric and threshold where possible
• How many observed time-study samples per task do you consider defensible for establishing a standard in a unionized site? Options: 10–25 samples, 26–50 samples, 51–100 samples, More than 100 samples
• Which discrepancy between measured productivity and WMS task counts would be a fatal data integration problem for you? Options: >2% discrepancy, >5% discrepancy, >10% discrepancy, Any unexplained discrepancy is fatal

The alternatives on the table and your decision calculus

• If you chose to keep your current approach, what concrete evidence would have to exist to justify staying with it instead of changing tools or processes? Options: Stable or improving labor cost per unit, Clear per-associate standards from WMS, Low turnover and high morale, No executive pressure to change
• Which internal or vendor options are you actively evaluating in addition to an engineered standards approach? Options: WMS native labor module, Do it internally with CI team, Another LMS vendor, Workforce management system, No other options being considered
• How persuasive are reference accounts showing 12–20% improvement for your leadership, and what would make those references insufficient? Options: Very persuasive, Somewhat persuasive, Not persuasive, Depends on similarity of operation
• Has anyone inside proposed solving this without an outside vendor, and if so who and what was their proposed timeline? Options: Yes, CI proposed internal program, Yes, IT proposed internal build, No internal build proposed, Other
• What would have to be true about your incumbent solution for you to keep it rather than switch to an engineered standards approach? Options: It provides defensible time standards, It integrates with WMS assignments, It has supervisor adoption, It provides the needed ROI

Timing, budget owners, and the decision path

• Which budget owner must approve the pilot and what is their typical approval threshold in dollars or competing priorities? Options: DC operations budget owner, Regional operations leader, VP of Operations, VP of HR, Finance
• If the pilot meets acceptance gates, how quickly could you deploy to additional zones, and what internal step would most often slow that timeline? Options: Within 30 days, 30–90 days, 3–6 months, More than 6 months
• What internal review or committee must sign off before commercial terms are agreed, and how often does that committee meet? Options: Weekly ops review, Monthly executive committee, Ad hoc legal review, No formal committee
• If a pilot establishes the promised savings, what would be the single fastest path to secure initial funding for rollout? Options: Reallocate operations budget, Use CI project funds, Apply for special capex, Seek regional piloting funds

Final practical checkpoints before we scope work

• Who will be the named data owner for the pilot, including API access and user provisioning responsibilities?
• Confirm which integration endpoints and credentials are available today and which require provisioning, select all that apply Options: WMS assignment feed, Time clock system, HR roster, Badge or location data, None are available yet
• Do you have a target pilot start date and a firm blackout window for test activities such as peak season or inventory count? Options: Yes, target date available, Yes, but flexible, No target date yet, Peak season blocks next 3 months
• If any of the technical or people prerequisites are not met within your planned kickoff window, would you prefer to delay or run a narrower pilot? Options: Delay until prerequisites met, Run narrower pilot, Proceed regardless

• Solution Experience — Engineered Standards Walkthrough

• Confirm the current state and its cost
• You confirm the stated current-state description and agree the pilot must prove a measurable productivity delta versus baseline.
• Deliver a tailored pilot acceptance criteria spreadsheet listing baseline metrics, measurement methods, thresholds, and required data extracts within five business days.
• You agree that the demonstrated workflow for standards, supervisor coaching, and reporting will produce the evidence needed for the 60-day pilot acceptance gates.
• Map engineered standards to a core workflow
• Provide a sample export of WMS event logs for the proposed pilot zone covering at least two representative shifts.
• List the core tasks to include in the time studies and identify any known outliers or shift patterns that matter for standard creation.
• You validate the proposed pilot acceptance criteria and data sources for measuring productivity improvement and associate reaction.
• Supervisor coaching scenario
• Reporting, measurement, and pilot acceptance criteria
• You identify any remaining evidence or stakeholders required before the pilot starts.
• Identify the pilot zone and the supervisors who will participate in the 60-day pilot period.
• Validate mapping and acceptance criteria
• Mitigation for associate and union concerns

• Solution Experience — Engineered Standards Walkthrough
• Solution Experience Deck — Engineered Standards
• Solution Brief — Engineered Standards

• meeting
• slides
• document

People & Stakeholders

• Who are the primary stakeholders for change and adoption at this site? Options: DC Director, Operations Manager, Continuous Improvement Lead, HR/People Leader, Union Representative, Supervisors, IT/WMS Lead, Other
• Please provide the name and role of the primary day-to-day contact for the pilot.
• Which teams must be consulted before you share changes to performance measurement with associates? Options: Operations, HR/People, Labor relations, Health & Safety, IT/WMS, Legal/Compliance, Union reps, Other
• Are there standing committees or forums where workforce measurement changes are discussed? Options: Yes - regular meetings, Yes - ad hoc meetings, No, Unsure
• Who typically approves final associate communications about changes to work measurement or incentives? Options: HR leader, Operations leader, Labor relations, Joint committee, Other

Union & Labor Relations

• Is a union present at this site? Options: Yes - single bargaining unit, Yes - multiple bargaining units, No, Unsure
• If a union is present, what is the established process for introducing changes to work measurement or incentive programs?
• Are there collective bargaining agreement clauses that govern time studies, performance measurement, or incentive pay? Options: Yes, No, Unsure
• If such clauses exist, please summarize any constraints or approval steps they require.
• Has the union previously accepted engineered standards or time study methods at this operation or elsewhere within the organization? Options: Yes - accepted, Yes - contested but resolved, No - rejected, No experience, Unsure
• Please provide the union contact or liaison who should be involved in pilot discussions.

Associate Communication & Change Plan

• Do you have a communication plan for associates about the pilot? Options: Yes - detailed plan, Yes - high-level plan, Not yet, Unsure
• Which channels will you use to tell associates about the pilot? Options: All-staff meetings, Supervisor briefings, Printed notices, Shift huddles, Digital messages (email/text/app), Union reps, Other
• Who will deliver the initial message to associates about measurement and why? Options: Site leader, HR/People leader, Supervisor, Union rep, Joint representative, Other
• What are the top messages or assurances you want associates to hear about the pilot (brief list)?
• Will you run listening sessions or focus groups with associates as part of the pilot? Options: Yes - before pilot, Yes - during pilot, Yes - after pilot, No, Unsure
• Do you plan to share individual productivity data with associates during the pilot? Options: Yes - real-time, Yes - periodic summaries, No - aggregated only, Undecided
• If you will not share individual data, how do you plan to address transparency concerns?

Incentives & Pay Preferences

• Do you intend to link incentives to measured productivity during the pilot? Options: Yes - immediately, Yes - after measurement period, No - measurement only, Undecided
• Which types of incentive schemes are acceptable or preferred? Options: Hourly bonus, Piece-rate, Team-based bonus, Spot rewards, Non-monetary recognition, Other
• Are there payroll, tax, or legal constraints that affect incentive design at this site? Options: Yes, No, Unsure
• If constraints exist, please describe them or note required approval steps.
• What range of pay variance due to incentives would be acceptable as a percent of base pay? Options: 0-2%, 2-5%, 5-10%, 10%+, Undecided
• Who must approve the final incentive formula for the pilot? Options: HR/People leader, Operations leader, Finance, Labor relations, Joint committee, Other
• How will incentives be funded during the pilot? Options: Pilot budget, Operating budget, Contingency reserve, Undecided

Supervisor Capacity & Coaching

• How many supervisors will be assigned to the pilot zone? Options: 1, 2-3, 4-6, 7+, Unsure
• What is the typical span of control (associates per supervisor) in the pilot area? Options: <10, 10-20, 21-40, 41-80, 80+
• Do supervisors currently use real-time dashboards or coaching tools? Options: Yes - regularly, Yes - occasionally, No, Unsure
• How much time per shift can supervisors reasonably dedicate to coaching and performance review? Options: <15 minutes, 15-30 minutes, 30-60 minutes, 60+ minutes, Varies by shift
• What training or support do supervisors need to interpret standards and coach effectively?
• Are there language, literacy, or shift-pattern constraints that will affect coaching delivery? Options: Yes, No, Unsure
• If yes, please describe the key constraints.

Baseline Retention & Workforce Metrics

• What is the current voluntary turnover rate for frontline associates (12-month rolling)? Options: <10%, 10-20%, 21-30%, 31-50%, 50%+, Don't track
• What is the average tenure for frontline associates at this site? Options: <3 months, 3-12 months, 1-3 years, 3+ years, Don't track
• Which baseline workforce metrics do you track today (attendance, absenteeism, shrinkage, etc.)?
• Do you have data on performance-related separations (terminations or resignations linked to performance)? Options: Yes, No, Unsure
• If available, please provide counts or rates for performance-related separations over the last 12 months.
• Would you be willing to share anonymized associate-level retention and performance data for pilot evaluation? Options: Yes, Yes - with privacy controls, No, Need legal review

Risks, Mitigations & Success Signals

• What are your top concerns about introducing engineered standards and measurement at this site?
• Which mitigation strategies would you consider using during the pilot? Options: Joint communication with union, Phased rollout, Shadow measurement period, Incentive-free measurement, Pilot with feedback loops, Supervisor-led coaching, Other
• Which specific success signals would make you comfortable expanding beyond the pilot? Options: Measured productivity improvement, No increase in turnover, Positive supervisor feedback, Positive associate survey results, WMS integration validated, Other
• What minimum time period do you consider necessary to evaluate adoption and retention impact? Options: 30 days, 60 days, 90 days, 180 days, Other
• Who will sign off on acceptance criteria related to change and adoption? Options: Operations leader, HR/People leader, Labor relations, Joint committee, Other

Practical Logistics & Next Steps

• When can you make supervisors and a pilot cohort available for initial training? Options: Within 2 weeks, 2-4 weeks, 1-2 months, Later / Unsure
• Is there a preferred timing for associate communications about the pilot start? Options: Before pilot start, At pilot start, During pilot, After measurement-only period, No preference
• Who will be responsible for collecting associate feedback during the pilot?
• Are there site-specific constraints (multiple facilities, shift overlap, language needs) we should plan for?
• Is there anything else you want us to know about change readiness at this site?

• Capture Time-Study Observations for Core Tasks
• Develop Engineered Task Time Standards
• Configure Individual Productivity Tracking
• Integrate Platform with WMS Work Assignment
• Activate Parallel Standards Tracking Mode
• Configure Incentive Pay Calculation Engine
• Deploy Real-Time Supervisor Dashboard
• Provision Associate Mobile Productivity Access
• Enable Supervisor Coaching Alerts and Work Balancing
• Migrate Historical Timeclock and Productivity Data
• Configure Daily and Shift Productivity Reports
• Train Supervisors on Dashboard and Coaching Workflows

Capture Time-Study Observations for Core Tasks

• Provide the warehouse zone names or aisle ranges that should be included in time-study observations (use your internal zone IDs where possible).
• List the core task types you want observed (examples: single-piece pick, batch pick, putaway, pallet build).
• State the number of associate observations per task you consider statistically meaningful for a pilot (examples: 10, 30, 50). Options: 10, 30, 50, Custom
• Name the floor-level artifacts we should collect during each observation (time stamped pick confirmations, tote IDs, SKU weight/pack info, operator badge ID).
• Attach or describe any existing time-study templates or video-capture consent forms you require us to use. Options: We have a template to share, No template; you will provide, Other
• Confirm any union or site-level notification windows required before observers start (e.g., 48-hour notice to workforce council). Options: No notice required, 24 hours, 48 hours, Custom

Develop Engineered Task Time Standards

• Describe the SKU characteristics or task constraints that must be modeled into standards (examples: heavy items, odd-dimension cartons, multi-sku picks).
• Provide the task element granularity you require for standards (element-level seconds, whole-task minutes, percentile-based allowances). Options: Element-level (seconds), Whole-task (minutes), Percentile allowances (e.g., 85th), Custom
• Define the variability rules to apply (seasonal peak adjustments, weight-based adders, break-pack allowances).
• Who will be the named approver for each engineered standard (title or role, e.g., DC Director, Labor Relations rep)?
• Specify whether standards should be segmented by shift, by work area, or by pay band. Options: By shift, By work area/zone, By pay band, Combination
• Indicate any historical standard documents or previously published time studies we must reconcile to avoid conflicts. Options: Yes - will share, No previous documents, Not sure

Configure Individual Productivity Tracking

• Provide the exact associate identifier field you want used to match activity to payroll (badge ID, employee number).
• List the WMS events that should be treated as productivity anchors (examples: pick confirm, pack confirm, dock scan).
• Specify the update cadence for per-associate productivity visibility (real-time, 1-minute, 5-minute, shift-end). Options: Real-time (<10s), 1 minute, 5 minutes, Shift-end
• Identify any privacy constraints or collective-bargaining clauses that restrict showing individual-level metrics to supervisors. Options: No restrictions, Restricted view for stewards/HR, Full anonymization required, Custom rules
• Who will own daily exception triage when an associate's tracked activity lacks a matching timeclock or WMS event (role/title)?
• Describe the reconciliation rule you prefer when an associate works multiple zones in a single shift (attribute by zone-of-origin, by time-weighted, or other). Options: Zone-of-origin, Time-weighted, Manual allocation, Custom

Integrate Platform with WMS Work Assignment

• Provide the name of your integration endpoint for the WMS (API base URL or integration queue name) and whether a staging endpoint is available.
• Select which WMS API surfaces you can expose for the pilot: work assignment queue, task status updates, inventory location, assignment reconciliation. Options: Work assignment queue, Task status updates, Inventory location, Assignment reconciliation
• Provide the expected peak task assignment throughput for the pilot zone (tasks per minute) to size call volume. Options: <1 t/min, 1-5 t/min, 5-20 t/min, Custom
• Specify the authentication method available for the integration endpoint (API key, OAuth2 client credentials, SFTP batch). Options: API key, OAuth2, SFTP, Other
• When will you be able to provide test credentials and a sandbox organization for validation? Options: Within 1 week, 1-2 weeks, 2-4 weeks, Not available
• What maximum allowable task-assignment mismatch rate between the platform and your WMS during parallel tracking will be considered acceptable for the pilot (this is an acceptance gate)? Options: <1%, 1-3%, 3-5%, >5%, Custom

Activate Parallel Standards Tracking Mode

• Provide the pilot zone(s) and SKU families that will run in parallel tracking mode without incentives.
• When do you plan to start parallel tracking relative to standards sign-off (immediately, after training, after WMS integration test window)? Options: Immediately after sign-off, After training, After integration tests, Custom
• Who will own daily monitoring and issue triage during parallel tracking (role/title)?
• For acceptance: specify the minimum measured productivity improvement versus your baseline and the rolling window method (example: 10% uplift measured as 7-day rolling average over a 60-day pilot). Options: No explicit target, >=5% uplift, >=10% uplift, >=15% uplift, Custom
• Specify the parallel tracking duration you require to validate standard stability for the pilot zone (examples: 14, 30, 60 days). Options: 14 days, 30 days, 60 days, Custom
• Indicate the baseline datasets you want used for comparison (examples: last 90 days shift-level picks per hour, timeclock vs throughput).

Configure Incentive Pay Calculation Engine

• Select which incentive structures you want modeled for the pilot (threshold top-up, graduated percentage, flat bonus per unit). Options: Threshold top-up, Graduated percentage, Flat bonus per unit, No incentives during pilot
• Describe the base pay and bonus calculation formula you prefer (example: base hourly + $0.05 per piece over standard).
• Provide the payroll endpoint or file format that must consume incentive payout data (example: payroll CSV, direct payroll API). Options: Payroll CSV export, Direct payroll API, Manual upload, Other
• State the payroll cutoff and pay-window constraints we must respect when scheduling incentive calculations.
• Are there documented collective-bargaining rules that limit incentive frequency or payout structure we must encode? Options: Yes - will provide, No, Unknown
• Who must approve final incentive rules before any live payout (title or role)?

Deploy Real-Time Supervisor Dashboard

• Provide the supervisor roles and the exact KPIs you require on the primary dashboard (examples: current labor efficiency %, backlog minutes, top 5 low performers).
• Select the device form factors supervisors will use for the dashboard (desktop, tablet, handheld). Options: Desktop, Tablet, Handheld
• Specify the maximum acceptable dashboard update latency for real-time metrics (examples: <10s, 30s, 1min). Options: Real-time (<10s), Near-real-time (10-60s), 1 minute, 5 minutes
• Identify any compliance or HR view restrictions for dashboards (examples: HR-only view of PII, steward-only access).
• Provide sample report layouts or screenshots of existing supervisor views we should emulate. Options: Will provide samples, No samples available
• Who will be responsible for dashboard acceptance testing and sign-off (role/title)?

Provision Associate Mobile Productivity Access

• Provide the make/model or class of mobile scanning devices associates currently use (example: handheld scanners, company smartphones).
• Select the associate-facing features required on mobile (real-time scorecard, task hinting, error reporting). Options: Real-time scorecard, Task hinting, Error reporting, No associate UI during pilot
• Specify language requirements for associate UI during the pilot (examples: English, Spanish, other). Options: English, Spanish, Other
• Are devices managed by your mobile device management (MDM) policy that restricts installing new apps? Options: Yes - MDM restrictions, No MDM restrictions, Unknown
• Describe authentication method for associates on devices (badge tap, persistent login, PIN) and any session timeout rules. Options: Badge tap, Persistent login, PIN, Other
• Provide any sample associate communications (emails, flyers) you plan to use so the platform messaging aligns during pilot. Options: Will provide samples, No communications available

Enable Supervisor Coaching Alerts and Work Balancing

• Provide the alert triggers you want for coaching (examples: below 80% of standard for 15 minutes, repeated quality errors).
• Select the delivery channels for alerts (dashboard banner, in-app notification, SMS, email). Options: Dashboard banner, In-app notification, SMS, Email
• Describe the actions a supervisor can take from an alert (reassign tasks, issue a coaching note, pause incentives).
• Who has authority to rebalance work between associates during a shift and what approvals are required (role/title)?
• Outline the escalation path if coaching alerts are not acknowledged within your defined SLA (examples: escalate to area manager).
• Indicate the data elements that must appear in each coaching alert to support a fair conversation (task-level times, recent activity window, exception notes).

Migrate Historical Timeclock and Productivity Data

• In which file formats can you export historical timeclock and productivity records for migration (examples: payroll CSV, database dump)? Options: Payroll CSV, Database dump, Punch-clock export, Other
• How many months of history do you want migrated for baseline analytics (3, 6, 12 months)? Options: 3 months, 6 months, 12 months, Custom
• For acceptance: what minimum migration completeness and data accuracy threshold (%) for historical timeclock and productivity records do you require to proceed to pilot? Options: >=90%, >=95%, 100%, Custom
• Who will validate migrated records against payroll and sign off on reconciliation issues (role/title)?
• Are there personally identifiable information (PII) masking rules we must apply when staging historical records for analytics? Options: Mask PII, No masking required, Custom rules
• Provide any known schema differences or field-mapping rules between your timeclock export and the platform's ingest schema. Options: Will provide mapping doc, No mapping doc available

• decision_readiness
• success_criteria
• gaps
• current_state
• stakeholders
• desired_state
• decision_readiness
• desired_state
• stakeholders
• gaps
• success_criteria
• current_state
• stakeholders
• decision_readiness
• current_state
• desired_state
• success_criteria
• gaps
• decision_readiness
• decision_readiness
• decision_readiness
• decision_readiness

• Master Services Agreement (MSA)
• Statement of Work (SOW) — Pilot & Rollout
• Order Form / Subscription Agreement
• Pilot Acceptance Criteria & Gates
• Pilot Acceptance Certificate
• Incentive Rules Addendum
• Data Processing Agreement (DPA)
• Integration Responsibility Schedule
• Service Level Agreement (SLA) — Production
• Change Order Agreement
• Termination & Data Return Addendum

• Go-live Health Check (weeks 1-4)
• First Measurement Review (weeks 4-10)
• Acceptance Gate Review (around day 90)
• Quarterly Success Review
• Annual Realization Review

• Close or schedule fixes for high-priority integration defects and publish the resolution timeline.
• Publish the signed acceptance decision or the conditional acceptance log with remediation items and deadlines.
• Execute the incumbent system wind-down plan or set it to read-only and archive historical data as specified.
• Schedule verification windows for any conditional remediation items and list required evidence for closure.
• Trend review of key outcome metrics
• Confirm sustained productivity gains against targets recorded in the Solution Scope or document variance reasons.
• Agree the prioritized backlog of defects and enhancements to address in the next quarter.
• Ensure associate survey action items are assigned and tracked to mitigate retention risk.
• Re-confirm success criteria and owners
• Publish associate survey findings and a concrete action plan to address top concerns.
• Validate retention impact by reconciling platform data with HR retention reports and update the dashboard.
• Annual outcomes versus targets
• Confirm whether year-to-date productivity and retention outcomes meet the expectations recorded in the Solution Scope.
• Finalize a prioritized 12-month enhancement backlog with delivery windows.
• Agree a reduced ongoing monitoring cadence and the owners for continued realization tracking.
• Publish the annual performance report and distribute to stakeholders for record.
• Create the prioritized enhancement backlog with target delivery quarters and verification criteria.
• Set the ongoing monitoring cadence and owner list for realization metrics tracking.
• Deployment validated for basic data flows and a short list of critical blockers is agreed.
• Owners confirmed for each success criterion recorded in the Solution Scope.
• Date set for first measurement readiness and verification tasks assigned as action items.
• Publish the deployment validation checklist and outstanding blocker list for async updates.
• Run a verification job to confirm WMS integration field mappings in a staging window.
• Circulate supervisor training completion report and schedule follow-up coaching sessions where gaps exist.
• Confirm the acceptance gate date and the evidence package required for the acceptance decision.
• Present first measurement vs targets
• Determine whether throughput per labor hour and labor cost per unit shipped are trending toward targets recorded in the Solution Scope.
• Identify top 2 root causes for any shortfalls and agree concrete corrective actions with timelines.
• Conduct targeted time studies in the pilot zone to validate element timings where variance is highest.
• Implement agreed WMS-to-platform field mapping corrections in a staging window and run reconciliation tests.
• Update supervisor coaching checklist and schedule focused coaching sessions for supervisors showing low dashboard engagement.
• Restate acceptance criteria and evidence required
• Produce a documented acceptance decision with a named signatory for managed acceptance scenarios.
• Confirm decommissioning approach for the incumbent system including data archive or read-only status.
• Where criteria are conditional or failed, agree remediation tasks and a final verification timeline.
• Supervisor adoption and behavior review
• Retention and associate impact review
• Present outcome data against each criterion
• Validate supervisor adoption signals
• Deployment and integration validation
• Root cause diagnosis for KPI gaps
• Associate feedback and retention impact
• Enhancement backlog and roadmap prioritization
• Early adoption and training signals
• Document pass fail and capture acceptance
• Open issues and enhancement backlog triage
• Lessons learned and continuous improvement actions
• Agree corrective actions and timeline to acceptance gate
• Incumbent system wind-down
• Blockers and open issues
• Agree immediate remediation actions
• Agree remediation plan for any failed or conditional criteria