Starting Together — a quick check to get us rolling

• Who will be our primary day-to-day contact for this program on your side? Options: Quality Director, VP of Operations, Manufacturing IT Manager, Plant Manager, Other
• Briefly, what triggered you to engage on traceability now (select all that apply)? Options: Recent product recall, Customer complaint / return, Regulatory audit or inspection, Internal quality finding, Continuous improvement initiative, Other
• Which production lines or sites are you initially considering for this effort?
• Who on your team has previously been through a traceability rollout or recall-simulation exercise? Options: Quality team members, Operations leads, IT/MES engineers, Supply chain/Logistics, No one, Other
• What would you like us to accomplish in our first working session together?

Who's Holding the Keys? — naming accountability and authority

• Who will be held accountable if a future recall cannot be narrowed to economically acceptable scope, and what decision authority do they hold? Options: Quality Director (process/recall decisions), VP of Operations (operational authority), CFO/Finance (budget sign-off), Plant Manager (site authority), Head of IT (tech/security authority), Other
• List every person or role that must approve go/no-go decisions (budget, timelines, pilot acceptance) for this project.
• Who is the economic buyer for traceability improvements, and what budgeting channel will be used? Options: Capital budget (CapEx), Operating budget (OpEx), Shared site budget, Corporate programs, Customer-funded, Other
• Who will be the technical owner responsible for integrating our platform with MES/ERP/equipment? Options: Manufacturing IT Manager, MES Administrator, External systems integrator, Plant automation engineer, Other
• Are there external stakeholders (customers, regulators, contract manufacturers) who must be engaged in decisions? If yes, who and why?
• Which stakeholder(s) are most likely to block progress if concerns aren't resolved, and what is their typical objection? Options: IT/security concerns, Production throughput impact, Cost/ROI skepticism, Supply chain disruption, Vendor lock-in concerns, Other

The Clock Is Ticking — hard dates, soft windows, and why speed matters

• If we had to accelerate this program to mitigate the next recall within 60 days, would your organization have the authority and resources to do so? Options: Yes, Possibly with executive escalation, No, timeline unrealistic, Unsure / need to confirm
• What fixed deadlines, audits, or customer commitments must we align to (enter dates and descriptions)?
• Which internal calendar windows will constrain implementation (plant shutdowns, peak seasons, audit freezes, budget cycles)? Options: Scheduled maintenance / shutdown, Peak production season, Regulatory audit windows, Year-end financial close, Procurement blackout, Other
• How soon do you expect a decision after we finish discovery and recall-simulation (select one)? Options: Immediately / within 2 weeks, Within 1 month, 1–3 months, 3+ months, Tied to budget cycle
• How does the current timeline pressure affect your team emotionally—urgent and energized, stretched and anxious, skeptical, or something else? Options: Urgent and focused, Stretched but committed, Anxious / risk averse, Skeptical / waiting for proof, Other

What 'Good' Actually Looks Like — vivid outcomes for each person who cares

• For the Quality Director: name the top three observable outcomes that would make this a clear win for you. Options: Narrower recall scope, Ability to trace to raw lots within 30 minutes, Complete genealogy per finished unit, Actionable audit trail, Reduced manual investigation time, Other
• For the VP of Operations: what operational metrics must remain unchanged or improve for you to accept the solution? Options: No decrease in throughput, Less than X% added cycle time, Operator headcount unchanged, Reduced recall-related downtime, Improved overall equipment effectiveness (OEE), Other
• For Manufacturing IT: what technical guarantees do you need around interfaces, security, and maintainability? Options: Standard APIs/REST, No changes to core MES, Role-based access control, On-premises option, Support SLAs, Other
• Which stakeholder's acceptance criteria are non-negotiable (select one or name another)? Options: Quality Director, VP of Operations, Manufacturing IT, Plant Manager, Regulatory/Compliance, Other
• How will your organization visibly show that the project delivered value (examples: internal memo, audit report, KPI dashboard)? Options: Updated SOPs, Regulatory audit sign-off, Executive summary with savings, Operations performance dashboard, Customer reference, Other

Invisible Roadblocks — the political, technical, and human frictions

• Which internal force would be most likely to quietly kill this project if left unaddressed? Options: MES vendor resistance, IT security objections, Operator union concerns, Finance withdraws funding, Site operations reprioritize, Other
• Which legacy systems or processes have previously caused projects to stall here (list systems and the nature of the issue)?
• How often do operators skip manual tracking steps under production pressure, and why does that happen? Options: Regularly / daily, Often / weekly, Occasionally, Rarely, Unknown
• Who inside your organization typically pushes back on hardware installs at workstation level, and what is their usual concern? Options: Plant engineering (space/route), IT (security/connectivity), Operations (throughput impact), Procurement (cost), Other
• Tell us about a past integration that failed or required custom development—what went wrong and how long did remediation take?

Data & Integration Reality Check — the facts that decide feasibility

• If asked right now, could you produce a genealogy linking a finished SKU to all raw material lot numbers within 30 minutes? Options: Yes, reliably, Only with manual effort and longer than 30 minutes, No — major gaps, Unknown / need to investigate
• Which systems store the lineage or lot data today (select all that apply)? Options: ERP, MES, LIMS, Warehouse Management (WMS), Manual paper records, Custom databases, Other
• Which data-capture methods are available on your lines today (select all that apply)? Options: 1D barcode, 2D barcode, RFID, Machine vision (direct part mark), PLC/serial device integration, Manual entry, Other
• Do you have sample production data and traceability records available for a recall-simulation? If yes, are there restrictions for sharing? Options: Yes – ready to share, Yes – needs data anonymization, No – will need export work, Restricted by legal/security
• Which lines or equipment lack digital outputs today and would likely require custom integration work?
• Who owns the credentials and network access we would need for integrations, and who is the right contact to request them?

Decision Economics — who signs the check and the ROI story

• If the solution reduced recall scope by 50% but cost X, would you still pursue it — and who would make that call? Options: Yes — Quality/Operations, Yes — Finance approves, Depends on payback period, No — not convinced, Unsure / need analysis
• What is a meaningful internal ROI measure for this project (select up to two)? Options: Reduction in recall cost, Faster recall investigation time, Less product waste, Reduced labor for investigations, Regulatory risk reduction, Other
• What procurement or capital approval thresholds must be met (enter dollar amounts and process owners)?
• Would you consider a staged pilot funded from existing site budgets, or must this be a full capital request? Options: Pilot from site budget, Requires full CapEx request, Customer-funded pilot, Unsure
• How quickly do procurement and legal typically turn a standard SOW and software agreement in your organization? Options: <2 weeks, 2–4 weeks, 1–2 months, 2+ months, Varies widely

Acceptance Gates & Timing — the tests that must be passed

• If our recall-simulation proves lineage in 30 minutes in a lab but parallel-run on the floor shows 10% operator misses, would you accept that result? What would you require next? Options: Accept and remediate later, Require production-level performance before acceptance, Require additional operator training and re-test, Other
• Which quantitative thresholds must we meet for acceptance (select all that apply)? Options: Genealogy query < 30 minutes, Query success rate > 99%, Throughput impact < X%, Operator error rate < Y%, System resilience to outage with <Z min recovery
• Who needs to sign each acceptance gate (design, pilot, full deployment)? Please list names/roles and their approval authority.
• What evidence will you require to accept the system (logs, test scripts, parallel run results, operator sign-offs)? Options: Recall-simulation report, Parallel-run KPI dashboard, Operator acceptance sign-off, Audit trail review, Other
• Are there regulatory or customer acceptance criteria that add extra gates (e.g., 3rd-party audit, customer witness test)? If yes, describe.

Communication & Escalation Rhythm — who we call when things get hard

• If a critical blocker appears during integration, who must be notified immediately and who is empowered to make trade-off decisions?
• What cadence of meetings do you prefer for progress and governance (select one)? Options: Weekly working session, Bi-weekly steering meeting, Monthly executive review, Ad-hoc as issues arise
• What communication channels do you prefer for rapid issues vs. formal updates? Options: Email for formal updates, Slack/MS Teams for rapid issues, Phone calls for critical issues, Ticketing system only, Other
• Who must be present for milestone demos or recall-simulation reviews (roles or names)?
• Is there an internal change control or CAB process that will gate releases or integration changes? If so, explain timelines and who sits on it.

Commitment Snapshot — capturing what we’ll agree to next

• If you had to pick one deliverable from discovery that would make this project go forward, what would it be? Options: Successful recall-simulation, Signed SOW for pilot, Budget approval, Integration feasibility report, Customer reference, Other
• What immediate access or artifacts do we need from you to start (select all that apply)? Options: Sample production data, MES/ERP access or API details, Network/PLC connectivity contact, Floor layout and process flows, Operator SME time, Other
• What are the top 3 risks you want explicitly mitigated in the SOW or pilot scope?
• Who will provide the final sign-off to proceed to pilot, and what date should we target for that handover?
• What would make you confident enough to introduce us to other plants or peers as a reference following discovery? Options: Clear ROI evidence, Smooth pilot with no production impact, Strong operator acceptance, Regulatory/audit success, Other

Start With What's Real (Quick Inventory)

• Which plant(s) and production line(s) should we focus on first for mapping the current state?
• Which of these best describes the product families passing through the target line(s)? Options: Single SKU high-volume, Multiple SKUs with similar process, Many SKUs with different routings, Custom/Job‑based production, Other
• Roughly how many finished units per hour (or per shift) flow through the candidate line(s)? Options: <100/hr, 100–500/hr, 500–2,000/hr, 2,000–10,000/hr, >10,000/hr, Not sure
• Which shifts and operators run these lines (days, nights, weekend patterns)? Options: Single shift, Two shifts, Three shifts, Intermittent/batch schedule, Mixed across sites, Not sure
• Who on your team will be the primary contact(s) for walkthroughs, access requests, and system owner permissions?
• Do you have existing network diagrams, PLC/SCADA access maps, or equipment inventory we can review before the walkthrough? Options: Yes — full docs available, Partial documentation available, Only high-level network maps, No documentation available, I need help locating them

Why Your Traceability Feels Fragile

• If traceability gaps caused an over-broad recall again, what would that mean for your team—operationally and personally?
• Thinking back to the last time you couldn’t narrow a recall: how long did it take to identify the suspect finished goods and why did that timeframe matter? Options: <1 hour, 1–4 hours, 4–24 hours, 1–3 days, >3 days, I don't remember
• What were the top three consequences from that event (e.g., customer penalties, line stoppage, disposal costs, regulatory inquiry, brand damage)? Please list and prioritize.
• How confident do you feel today that a cross‑equipment genealogy (finished good → raw inputs → test results) could be produced within your recall SLA (e.g., 30 minutes)? Options: Very confident, Somewhat confident, Low confidence, Not confident at all, We have no SLA
• When things go wrong, who usually feels the heat internally (Quality, Ops, IT, Legal, Executive)? Options: Quality, Operations, Manufacturing IT, Supply Chain/Logistics, Legal/Compliance, Executive Leadership, Other
• How does that pressure show up day‑to‑day—e.g., extra emails, expedited lab tests, halted shipments, or informal workarounds? Give a concrete recent example.

Where the Data Actually Lives — and Where It Dies

• If we asked you to run a full genealogy trace right now, which systems would we need access to but currently aren’t integrated? Options: ERP (e.g., SAP, Oracle), MES, LIMS/QC systems, PLC/SCADA historians, Test/inspection equipment, Warehouse/TMS, Paper logs/manual records, Other
• Which of these systems are currently the authoritative source for lot/serial identifiers on your floor? Options: MES, ERP, Manual paperwork, Local databases, Equipment-generated tags, No single authoritative source, Other
• How frequently is identifier data captured at key steps (e.g., receiving, assembly, test, packing)? Options: Real-time/event-driven, Near real-time (minutes), Batch sync (hourly/daily), Only at shift end, Only on paper, Varies by station
• Who owns the interfaces between these systems today (IT, OT team, third‑party integrator, none)? Options: IT, OT/controls, Quality engineering, External integrator, No clear owner
• Do you have sample extracts (CSV/XML) or API endpoints we can use to prototype a genealogy now? If yes, please describe availability and format.
• What data retention or archival rules might limit access to historical batch data we need for recall analysis? Options: Retained >7 years, Retained 1–7 years, Retained <1 year, Archived offsite/unavailable, Unknown

The Physical Reality: Labels, Readers, and the Things That Break

• Which parts of your production flow most often lose track of IDs—are there stations where identifiers routinely fail to survive the process? Options: Receiving/Incoming, Material preps (wash/coat), High‑heat operations (bake/autoclave), Wet/process lines, Robotic handling, Packing/shrinkwrap, Shipping, Not sure
• What identifier technologies are currently used across the line(s)? Select all that apply. Options: 1D barcode/labels, 2D datamatrix, RFID (HF/UHF), Direct Part Mark (DPM), Machine vision OCR, Manual operator entry, None/primarily paper
• How often do identifiers fail inspection or read rates drop below acceptable levels, and what corrective actions are typically taken? Options: Daily, Weekly, Monthly, Rarely, Never tracked
• Describe environmental or process conditions that challenge identification (chemical exposure, high temp, abrasion, vibration, washdown). Which ones matter most?
• What is the typical maintenance cadence and spare‑parts availability for readers/scanners/cameras on the line? Options: Daily checks, Weekly, Monthly, On failure, No formal cadence
• How do operators feel about scanning or validation steps—are they seen as helpful, neutral, or a throughput bottleneck? Share an example. Options: Helpful, Neutral, Seen as bottleneck, Mixed/varies by shift

Recall Simulation: Past Lessons and Unseen Gaps

• When you replayed your last recall exercise (real or tabletop), what single gap surprised you the most?
• Which recall metrics are most important for your team to improve (pick up to 3)? Options: Time to identify affected lots, Precision of scope (fewer false positives), Confidence level for regulatory reporting, Time to notify customers, Cost of recall per incident, Root‑cause attribution clarity
• How quickly does your current tooling return genealogy queries for a test subset (e.g., one finished lot)? Options: <5 minutes, 5–30 minutes, 30–60 minutes, >60 minutes, Cannot complete query
• Have you ever run a recall simulation using production data end‑to‑end? If so, what failed (data, connectivity, query performance, interpretation)? Options: Yes — succeeded, Yes — failed due to data gaps, Yes — failed due to performance, No — never attempted, Not sure
• How would you describe the company’s tolerance for false positives during an investigation (conservative/broader vs. precise/lower scope)? Options: Very conservative (broader scope), Balanced, Prioritize precision (narrow scope), Undecided
• If we found a recurring data gap that caused over-broad recalls, what resources would you be willing to commit to closing it (engineering hours, budget, third‑party tools)? Options: Minimal (pilot only), Moderate (some engineering/time), Significant (cross‑team project), Unsure — need leadership approval

Integration Reality Check: What Will Make This Work (or Break It)

• What integration does your team quietly assume is impossible (but that, if solved, would make recalls trivial)?
• Which of these constraints shape integration feasibility at your site? Options: Strict IT security/firewall, No OT network access, Proprietary equipment with no API, Legacy MES with limited extensibility, Change control/red tape, Limited internal dev resources
• Do you have an established middleware or message bus (e.g., MQTT, OPC-UA, Kafka) we should plan to use? Options: Yes — OPC-UA, Yes — MQTT/Kafka, Yes — other middleware, No central middleware, Unsure
• What are your security and compliance requirements for any agent/connector on the floor (e.g., network zones, encryption, signing, approval process)?
• How many custom device interfaces (equipment without standard outputs) do you expect will require bespoke work? Options: None, 1–3, 4–10, >10, Unknown
• What timeline constraints do we need to respect for integrations (maintenance windows, regulatory deadlines, launch dates)? Options: Immediate/ASAP, Within 1–3 months, 3–6 months, 6–9 months, Year+ or not defined

People, Process, and Permission: Who Moves the Needle?

• Who could quietly block a traceability project even if the budget and exec sign‑off are in place? Options: Plant Manager, IT Security, Maintenance/OT, Operators/Union, Quality Leads, Supply Chain, Other
• Which stakeholders must be convinced before a pilot becomes a funded rollout? Options: Quality Director, VP of Operations, Manufacturing IT Manager, Finance, Regulatory/Compliance, Site Leadership
• How do operators and supervisors currently get coaching or corrective actions when a traceability error is discovered? Options: Formal retraining/SOP update, Informal coaching, Quality tickets, No consistent process, Other
• What change-management risks keep you up at night around adding automated capture at the line (e.g., operators skipping steps, union issues, production slowdowns)?
• What internal success signals will convince leadership this is working (examples: reduced mean time to identify, fewer SKUs impacted, operator adoption rates)?
• Who will approve acceptance criteria for a pilot (names or roles), and what governance cadence do they expect for reviews?
• How does your quality/regulatory team prefer evidence for audits—screenshots, CSV exports, signed SOPs, or integrated immutable logs? Options: CSV/Exports, Immutable audit logs, Screenshots and reports, Signed SOPs and change logs, Combination

If We Had to Prove It in 30 Minutes — What Evidence Do You Insist On?

• If we delivered a 30‑minute recall simulation tomorrow, what specific outcomes would make you call it a success?
• Which artifacts should we bring or request up front to run a meaningful simulation (pick all that apply)? Options: Sample production data extract (CSV), Network/equipment diagram, Bill of materials/product structure, Last recall investigation report, Access to a test PLC or historian, Operator shift logs
• For pilot scope, would you prefer we start with a short SKU set, a single critical station, or an end‑to‑end line? Why? Options: Single SKU, Single station, End‑to‑end single line, Multiple lines small sample, Undecided — need advice
• What timing windows and access restraints should we plan around for on-floor work (preferred dates, maintenance windows, sanitation cycles)?
• What decision criteria and timeline will you use after a successful pilot to move to rollout (roles involved, budget signoff, target dates)?

Quick start — who’s on point?

• Who will be our single-day-of-deployment contact (name, role, phone/email) and the best hours to reach them?
• Which of these stakeholders must be present or available for deployment approvals? Options: Other, Quality Director, Manufacturing IT Manager, VP of Operations, Plant Manager, Controls/OT Lead, Supply Chain Lead, Security/IT Operations
• What communication channel should we use for minute-by-minute coordination on deployment day? Options: MS Teams/Slack channel, Phone conference bridge, Email thread, Dedicated ticketing incident, On-site radio/walkie
• Are there any planned plant events, production peaks or maintenance windows in the next 90 days we must avoid? Options: Yes — peak production dates, Yes — scheduled maintenance/shutdown, No scheduled conflicts, Unsure / need to check
• Are there vendor contracts, audits, or regulatory checks in the near term that constrain deployment timing?

What would make this go-live look like a nightmare?

• If this deployment went poorly and you had to justify it to the exec team, what single cause would you point to?
• Which of these failure modes concerns you most for pre-deployment and testing? Options: Unexpected throughput loss, Incorrect genealogy mappings, Missing or stale test data, Security or compliance breach, Unavailable owners during incident, Rollback failure, Other
• Have you previously experienced deployment-related production interruptions? Tell us the incident, root cause, and impact (downtime, recalls, regulatory exposure).
• What is the maximum acceptable production downtime (per line) during a test incident before escalation is mandatory? Options: Zero tolerance (no disruption), < 15 minutes, 15–60 minutes, 1–4 hours, > 4 hours
• Who in your organization has final authority to stop testing and declare an incident during deployment? Options: Plant Manager, Quality Director, Manufacturing IT Manager, Site EHS/Safety, Other

If we ran a recall-simulation tomorrow, would your test data hold up?

• Can your test dataset support a full trace from finished good to raw-material lot within 30 minutes? Options: Yes — proven, Yes — unproven (needs validation), No — gaps exist, Not sure
• Where does your test data originate and how is it linked to production identifiers (examples: MES exports, PLC logs, ERP lot records)? Describe sources and mapping approach.
• Which data sources can we access for testing? Options: MES, ERP, WMS, PLC/SCADA logs, Test equipment outputs, CSV/flat-file exports, Manual batch records, Other
• Are there regulatory or privacy constraints (masking, anonymization) that prevent sharing real identifiers for testing? Options: No constraints — real data allowed, Masking required but traceable mapping available, Masking required and mapping restricted, Unsure — need legal/QA input
• How often is your test data refreshed or synchronized with production (select the closest)? Options: Real-time / streaming, Hourly, Daily, Weekly, Manual snapshots on request, Never / ad-hoc
• Who will be accountable for delivering an approved, representative test dataset and signing off on its use?

Are the doors unlocked? — access, networks, and environments

• Which environments will our engineers need to access for pre-deployment validation and who currently controls each environment?
• Which of the following environment types must be opened to us? Options: Production (read-only), Production (write/config), Staging/Pre-prod, QA lab, Dev, PLC/OT network, Cloud account/tenant, On-prem servers or RDS, DMZ
• Do we need formal IT/OT tickets, vendor approvals, or maintenance windows to obtain access — and what is the typical lead time? Options: No approvals needed, Standard IT ticket (1–3 business days), Change control board approval (multi-week), Vendor-managed access (depends on vendor), Unknown — need help to determine
• Will our team receive individual accounts or will we be provisioned shared/service accounts for the work? Options: Individual accounts with auditable access, Shared service accounts, VPN access with jump-host, Vendor access through customer portal, Other
• Are there network protections we must provision (MFA, IP allowlist, jump-host, firewall rules) and who issues those changes? Options: MFA required, IP allowlist required, Jump-host required, Firewall rule changes required, No special network requirements, Unsure — need IT/OT guidance

Who will actually run the playbook?

• If an integration script or connector needs an emergency fix during testing, who in your organization has the authority and skillset to approve and implement the change immediately?
• Please provide primary and secondary owners (name, role, contact) for: IT, OT/Controls, Quality, Operations, Supply Chain, and Security.
• Which teams will be available and committed to be on-call during the scheduled deployment window? Options: IT, OT/Controls, Quality, Operations/Line Leads, Engineering, Third‑party vendors, Plant Management
• What is your internal escalation path and SLA expectations for unresolved deployment issues (response and resolution time targets)? Options: 1-hour response / 4-hour resolution, 4-hour response / 24-hour resolution, Same-business-day, Next-business-day, No formal SLA
• Does a Change Advisory Board or CAB need to approve configuration changes during the deployment window? Options: Yes — CAB approval required, Only for production-impacting changes, No CAB involvement, Unsure — need to verify

If things go sideways, what’s the plan to rewind?

• If a connector or configuration causes production anomalies, what exact rollback steps would you expect us to execute and who triggers them?
• Do you have documented rollback/runbook procedures for integrations and can they be executed without vendor involvement? Options: Documented and tested internally, Documented but untested, No documented rollback procedures, Vendor-run rollback only
• What are your RPO (how much data loss is acceptable) and RTO (how quickly must services be restored) targets for systems we will touch? Options: RPO < 1 minute / RTO < 1 hour, RPO < 15 minutes / RTO < 4 hours, RPO < 1 hour / RTO < 24 hours, Flexible / business decision, Not defined
• Are backups, snapshots, or database exports taken immediately before deployment and who owns that verification? Options: Yes — backups verified by IT, Backups scheduled but not verified, No backups planned, Unsure — need to confirm
• Would you prefer a staged rollback (disable connectors for one line first) or a full-system rollback if issues appear? Options: Staged rollback by line/area, Full-system rollback, Hybrid approach, Undecided — advise us

How will we prove this is safe to go live?

• What are the non-negotiable acceptance criteria that will convince you to promote from parallel-run to go‑live (be as specific as possible)?
• Which of these measurable signals must pass during validation? Options: Genealogy query speed within target (seconds), Recall-simulation completes within 30 minutes, No measurable production throughput loss, Operator task time within baseline, Data fidelity/field-level accuracy thresholds, Zero critical errors in logs
• Who has final sign-off authority for go‑live and in what format do they require acceptance evidence (signed form, email, dashboard metrics, meeting minutes)? Options: Signed acceptance form, Email approval, Recorded go/no-go meeting, Automated dashboard evidence, Other
• What duration and sampling plan do you expect for the parallel run before final acceptance (choose closest)? Options: One shift (sampled), Three shifts, One week, Two weeks, Custom plan — describe below
• After go-live, what monitoring cadence and support follow-up do you expect (first 24–72 hours and first month)? Options: Hourly checks first 24h, daily week1, weekly month1, Daily checks week1, weekly month1, On-demand support only, Dedicated on-site support for first week, Other

Final practicalities — logistics, training, and documentation

• Will operators and line technicians receive hands-on training during deployment or before go‑live, and who schedules it? Options: Hands-on during deployment, Pre-deployment classroom/virtual, Train-the-trainer model, No formal training planned, Other
• Which artifacts must be produced and accepted before we leave site (examples: environment access list, signed runbook, test dataset manifest, rollback checklist)? Options: Access list, Signed runbook, Test dataset manifest, Rollback checklist, Acceptance report, Knowledge transfer docs
• Are there documentation or audit requirements (e.g., CFR 21, ISO, internal) that our deliverables must meet? Options: Yes — regulatory (specify), Yes — internal audit standards, No special documentation requirements, Unsure — need to verify
• What would you like our team to do to make operations and QA comfortable with the new system during the first 30 days?
• Finally, what outstanding questions or blockers should we resolve before we schedule the pre-deployment readiness window?

Quick Site Snapshot — Start Here

• What's your role and primary responsibility for traceability and recalls? Options: Quality Director, Manufacturing/Plant Manager, Manufacturing IT Manager, VP of Operations, Supply Chain Manager, Other
• Which facility or product line are we focusing on for this conversation?
• Which regulatory frameworks most constrain this line's recall and traceability requirements? Options: FDA (US), EMA (EU), ISO standards, FSMA, Medical device MDR, Other regional regulator, Multiple/All of the above
• Roughly how many SKUs or unique part numbers flow through the target line per month? Options: <100, 100–999, 1,000–9,999, 10,000–99,999, 100k+
• Have you been directly involved in a recall or large traceability investigation in the last 36 months? If yes, briefly describe the outcome.

If You Had to Investigate a Recall Right Now, Could You?

• Imagine a customer complaint flags a finished good—could your team trace back to every raw-material lot within 30 minutes? Options: Yes, reliably within 30 minutes, Often, but requires extra effort, Sometimes—often longer than 30 minutes, No, not possible today
• How long does a typical recall investigation take today (from first report to a defensible scope estimate)? Options: <30 minutes, 30–60 minutes, 1–4 hours, 4–24 hours, >24 hours
• When you start an investigation, which sources do you consult first? Options: MES, ERP, Paper logs / binders, QC lab records, Operator testimony, Machine/tester logs, Other
• What are the single biggest blockers you hit when trying to narrow scope quickly? Options: Missing identifiers (labels fall off), System boundaries (data siloed in MES), Manual handoffs without timestamps, Legacy equipment without digital output, Poor lot granularity, No standard part identifiers
• Tell us about the last time you could not narrow a recall—what specific gaps prevented a tighter scope?

Where the Data Usually Breaks — Let's Name the Failure Modes

• Which piece of equipment, interface, or handoff is most likely to silently erase traceability on your line? Options: Receiving/Incoming inspection, Line OEE/PLC events, Inline testers, Packaging/labeling station, Manual rework or inspection stations, Shipping/dispatch
• Which data-capture methods are in use on the line we're discussing right now? Options: Barcode scanning, RFID reads, Machine vision (OCR/GS1), Direct part marking, Manual key-in, PLC/event pulse capture, Tester/equipment logs
• Do you have real-time integrations between equipment (PLCs/testers), MES, and ERP, or are there manual/periodic handoffs? Options: Fully real-time across systems, Partial real-time; some manual syncs, Mostly periodic batch transfers, Primarily manual processes/paper
• Have you had to develop custom interfaces to capture critical traceability data? If yes, how frequently and with what lead time? Options: Never, Occasionally (weeks), Frequently (months), Ongoing/custom project
• When an identifier is lost or unreadable (smeared, detached), what is the established operator or system contingency? Options: Rework and relabel, Hold batch for QA, Reconstruct from upstream logs, Use paper backup records, No formal contingency
• Are there process steps intentionally tracked only at batch/lot level rather than per unit? Where is that a deliberate trade-off?

Who Holds the Keys — Accountability, Ownership, and Operator Reality

• If traceability fails and a recall occurs, who in your organization typically bears the consequences—and do they have authority to make the necessary changes? Options: Quality/Regulatory, Plant/Operations, Manufacturing IT, Supply Chain, Legal/Compliance, Cross-functional steering team
• Who is the day-to-day owner of traceability data quality (role/title)?
• When operators perceive scanning or checks slow throughput, how do they most often behave? Options: Skip scans, Use shortcuts/aliases, Escalate to supervisor, Follow procedure regardless, Log workarounds on paper
• What training, incentives, or accountability mechanisms exist to encourage accurate data capture? Options: Formal classroom training, On-the-job coaching, KPI targets tied to bonuses, Periodic audits, None in place
• How have frontline teams reacted to previous technology rollouts—were they enabling, neutral, or resisted? Give an example. Options: Very positive and enabling, Mixed reactions, Mostly disruptive/resisted, Not applicable/no prior rollouts
• Share a short example where operator behavior either saved or significantly hindered a traceability investigation.

Speed, Scale, and the Moments That Break Your SLA

• If genealogy queries slow at peak load, what immediate outcome do you expect on the shop floor or in the investigation? Options: Production paused, Investigations delayed, Workarounds used (paper/reports), No noticeable impact
• What is your required time-to-scope for a regulatory recall investigation (what do regulators/plans expect)? Options: 15 minutes, 30 minutes, 1 hour, Several hours, No formal requirement
• At peak, how many units per hour across the affected lines must be traceable without impacting throughput? Options: <100 units/hr, 100–999 units/hr, 1,000–9,999 units/hr, 10,000+ units/hr
• What query response time from a traceability system would you consider acceptable under load during an investigation? Options: <1 second, <5 seconds, <15 seconds, <30 seconds, <1 minute, >1 minute
• How long can your site tolerate a network or power outage before traceability data loss or unacceptable risk occurs? Options: Seconds to minutes, Up to 1 hour, Several hours, A full shift, A day or more
• Do you currently publish or track an SLA for recall investigation response time and system availability? Options: Formal SLA (published), Internal targets only, No formal SLA or target

What Would Make You Sleep Easier — Clear, Measurable Success

• If you could pick one unarguable metric that proves traceability is solved, what would it be? Options: Time-to-scope (minutes), Percent reduction in recalled volume, Percent of units with complete genealogy, Query success rate within SLA, Other
• What percent reduction in unnecessary recalled volume would you deem a success for a pilot program? Options: 90%+, 70–89%, 50–69%, <50%, Unsure
• What target for genealogy query success rate (complete results within required time) feels acceptable? Options: 99.99%, 99.9%, 99%, 95%, Other
• Which acceptance criteria must a recall-simulation pilot meet for you to consider the solution viable? Options: Meet time-to-scope target, Integrations cover >90% touchpoints, No critical data gaps in sample runs, Operators accept the workflow, All of the above
• How would you prefer data resilience and outage handling be validated? (select all that apply) Options: Simulated power loss at station, Network outage and failover, Equipment disconnects during run, Replay of buffered data, Disaster recovery drill
• Describe what operator acceptance and day-to-day usability would look and feel like after a successful deployment.

Gates, Budget, and the Real Next Steps

• What would make you actually sign for a pilot within 90 days rather than leaving this on the to-do list? Options: Executive sponsorship, Clear ROI and payback, Minimal operational disruption, Reference from same industry, Budget allocated, Other
• Which internal approvals or committees must sign off before a pilot or commercial commitment? Options: Procurement, IT Security/Architecture, Plant Operations, Quality/Regulatory Council, Finance, Legal/Contracts
• What is your preferred timeline for pilot kickoff, integration sprints, and a go/no-go decision? Options: Pilot in 0–1 months, Pilot in 1–3 months, Pilot in 3–6 months, Pilot later than 6 months
• What ballpark budget range is available for a pilot and initial integration work? Options: <$25k, $25k–$100k, $100k–$500k, $500k–$1M, >$1M, Unsure
• List the top three contractual or commercial risks you'd require mitigation for before committing (e.g., custom integration effort, acceptance gates, warranty of data completeness).
• Who else (names/roles) should be involved in the next conversation to make sure decisions can move forward?