Quick Orientation — Who Are We Solving This For?

• Which best describes your primary role? Options: Director / Head of Quality, Validation Manager, IT Director / Head, QA Manager, Compliance / Regulatory Lead, Other
• In one sentence, what's the single outcome you most want from a validation engagement right now?
• Which system or system type is the focus for this conversation? Options: LIMS, MES, eQMS / QMS, Clinical data system / EDC, ERP, Custom / in-house application, Other
• What triggered the need for validation now? (select all that apply) Options: New implementation, Upgrade / change, FDA/EMA inspection observation, Internal audit finding, Vendor requirement, Other
• Roughly when does the system need to be released into production? Options: Within 4 weeks, 1–3 months, 3–6 months, 6–12 months, No firm date

If an Inspector Showed Up Tomorrow, What Would They See?

• If an inspector walked into your site next week, what's the first validation-related issue you worry they'd flag?
• How would you rate the system’s current inspection-readiness on a practical level? Options: Inspection-ready today, Mostly ready with a few gaps, Several major gaps, Not ready at all, Unsure
• Which specific documents or artifacts do you expect would be missing or weakest if reviewed?
• Have you had any inspection or audit observations related to CSV in the last 3 years? Options: Yes — open, Yes — closed, No, Unsure
• If a finding occurred, what would its most likely operational impact be? Options: Production pause / delay, Corrective action plan and resource drain, Escalation to senior leadership, Regulatory letter risk, Minimal operational impact

Where Validation Slows You Down (and Why You’ve Learned to Tolerate It)

• What's the one validation bottleneck your team treats as 'just how it is'?
• How many systems are currently in your validation backlog? Options: 1–5, 6–15, 16–50, 50+
• How many dedicated FTEs does your internal validation team have right now? Options: 0 (fully outsourced), 0–1, 1–3, 3–6, 6+
• Which factors most commonly cause delays in your CSV projects? (select up to 3) Options: Lack of validation staff, Incomplete vendor documentation, Unavailable test environments, Complex integrations, Change control backlog, Stakeholder availability
• When validation slips, how often does that push back production or release dates? Options: Almost always, Often, Sometimes, Rarely, Never

Who's Really Deciding — The People Who Speed It up or Stop It Cold

• Who in your organization can block or accelerate a validation project faster than anyone else?
• Which stakeholders must formally accept the validation deliverables? (select all that apply) Options: Quality Director, Validation Manager, QA Reviewer, IT Operations, GxP Compliance / Regulatory, Manufacturing / Operations, Vendor / Supplier, Other
• How does your Quality team define 'ready' vs. how IT defines 'ready' for a given system?
• What approval/escalation path do you prefer if timelines slip or scope grows? Options: Weekly steering update, Escalate to functional director, Open formal change request, Ad-hoc escalation via email/call, Other
• Once documentation is delivered, how quickly can your key approvers realistically sign-off? Options: Within 48 hours, 3–7 days, 1–2 weeks, Longer / depends

What 'Inspection‑Ready' Actually Looks Like for You

• If you could choose one non-negotiable requirement for being 'inspection-ready', what would it be?
• Which deliverables must be perfect for auditors in your view? (select all that apply) Options: Validation Master Plan, IQ / OQ / PQ Protocols, Traceability Matrix, Deviation and CAPA Records, Vendor Technical Documentation / SRS, Change Control History, CSV Summary Report
• How do you measure success for a validated system—what concrete signals tell you it worked? Options: High pass rate of tests, Zero open critical deviations, Auditor sign-off, On-time production release, No rework after go-live
• What level of test coverage is required for you to be comfortable (e.g., all protocol steps, risk-based, critical only)? Options: 100% of protocol steps, Risk-based coverage, Critical functions only, Other
• Who must personally feel confident before you would declare the pilot successful?

Where Hidden Scope Lives — Let’s Find the Surprises Before They Find Us

• Tell me about customizations or integrations you suspect will surprise us during testing.
• Which of these exist in the system today? (select all that apply) Options: Custom code / bespoke configurations, Third‑party integrations, APIs with other systems, Data migration tasks, Batch or manufacturing record interfaces, Cloud-hosted vendor-managed components, Unsure / unknown
• Are vendor Technical Documentation, SRS/URS, and qualification instructions available and current? Options: Complete and current, Partial / outdated, Not available, Unsure
• How many distinct environments do you have available for validation (development/test/qa/stage/prod)? Options: Single environment, Two environments, Three (dev/test/prod), Four or more, Unsure
• Estimate the likelihood that testing will uncover undocumented configurations that increase scope. Options: <10%, 10–30%, 30–60%, >60%

Pilot That Proves Value — What Would Convince You to Scale?

• What concrete pilot outcome would make you feel we've earned the right to validate more systems together?
• Which pilot scope would you prefer to start with? Options: MVP: critical workflows only, Full system validation, Focused module / feature, Documentation gap assessment only, Other
• What acceptance criteria must the pilot meet for your stakeholders (specific pass rates, no open critical deviations, timeline adherence)?
• What timeline is realistic for a pilot from environment access to a complete inspection-ready package? Options: 2–4 weeks, 4–8 weeks, 8–12 weeks, 12+ weeks
• Which commercial terms signal you're comfortable starting a pilot? (select all that apply) Options: Fixed-fee pilot, Time & materials with cap, SLA for turnaround times, Pilot discount toward program, Performance milestones

Before We Start — The Practical Things That Trip Projects Up

• What logistical detail has derailed your validation projects more than any other in the past?
• Which of these are already in place for this project? (select all that apply) Options: User/tester access, Test environments provisioned, Sample test data available, Vendor cooperation confirmed, Change control access, None of the above
• Who will be the day-to-day contact responsible for coordinating validation activities? Options: Validation Manager, Quality Lead, IT Project Manager, Vendor Contact, Other
• How much lead time does IT typically need to provision environments or access? Options: <1 week, 1–2 weeks, 2–4 weeks, 4+ weeks
• Do you have a current Validation Master Plan we should align to? Options: Yes — current, Yes — exists but outdated, No, Unsure

Commitments & Next Steps — What Would Make This Irresistible?

• What's the single condition that would make you sign-off to run a pilot this week?
• What budget or procurement status should we be aware of? Options: Approved budget available, Budget approval in progress, Requires new approval, No budget currently
• Who in your organization will negotiate / sign commercial terms for a pilot? Options: Procurement, Finance, Director of Quality, IT Leadership, Other
• What meeting cadence would you prefer during the pilot to stay confident and informed? Options: Daily standup, Weekly sync, Biweekly review, Milestone reviews only, Ad-hoc
• When would you like us to schedule a readiness check to confirm access, owners, and environments? Options: Immediately / this week, Within 1–2 weeks, Within 2–4 weeks, After internal approvals
• Are there any previous experiences, vendor behaviors, or internal processes you want us to explicitly avoid?

Quick Snapshot: Tell Us What’s Top of Mind

• What single system or application are you most urgently trying to validate right now?
• Which best describes your current validation workload right now? Options: A few high-priority systems (1–3), A moderate backlog (4–10), A large backlog (11–25), Mass backlog (>25)
• Who on your team owns validation decisions day-to-day? Options: Quality Director, Validation Manager, IT Director, QA/Validation Team Member, External consultant/contractor, Other
• Roughly how many full-time equivalents (FTEs) are dedicated to validation in your organization? Options: 0, 0.5–1, 2–3, 4–6, 7+
• If you had to name one thing keeping that system from being inspection-ready this month, what would it be?
• How soon do you need a fully inspection-ready validation package for that system? Options: Within 2 weeks, Within 1 month, 1–3 months, 3–6 months, Tbd/No fixed date

When Inspections Loom: Is That Your Trigger?

• Has an upcoming or recent regulatory inspection driven your current validation priorities? Options: Yes — immediately urgent, Yes — within the next 6 months, Not yet, but we’re concerned, No, business/IT timelines drive us
• What did the last inspection teach you about the state of your validation artifacts? Options: No findings, Minor observations, Formal observations requiring remediation, We received a warning letter
• When inspection pressure increases, where do you feel the most stress—regulatory risk, operational downtime, or internal politics? Options: Regulatory risk, Operational downtime, Internal politics/resource conflicts, Budget constraints, Other
• How would an inspection finding related to CSV affect your day-to-day operations or release timelines?
• How long has inspection risk been a recurring concern for your team? Options: Less than 6 months, 6–12 months, 1–3 years, Longer than 3 years
• If you had to prioritize, which outcome matters most right now: closing FDA observations, reducing backlog, or accelerating releases? Options: Close FDA observations, Reduce backlog, Accelerate releases, Improve documentation quality, Other

Where The Backlog Actually Lives (and Who’s Carrying It)

• How many systems are currently waiting for validation work to start (not in progress)? Options: 0, 1–3, 4–10, 11–25, 26+
• What’s the average age of items in that backlog? Options: <3 months, 3–12 months, 1–2 years, >2 years
• Which teams are the bottleneck for clearing the backlog (select all that apply)? Options: Validation/QA, IT/DevOps, Vendors, Product Owners, Clinical/Research, Other
• On a scale, how predictable are your validation lead times from start to inspection-ready package? Options: Very predictable, Somewhat predictable, Unpredictable, Chaotic
• How do you currently prioritize which systems to validate first? Options: Risk-based, Inspection-driven, Release schedule, Business impact, Ad-hoc/first-come
• Tell me about the last system you deprioritized—what made you delay it, and what happened as a result?

What Your Validation Artifacts Actually Say About You

• If someone read your current validation package for a system you care about, would they find a coherent master plan, or scattered documents? Options: Coherent master plan, Mostly coherent with gaps, Scattered documents, Minimal documentation
• How complete are your IQ/OQ/PQ protocols and execution records across typical projects? Options: Always complete, Usually complete with minor gaps, Often incomplete, Rarely complete
• Where do traceability and requirements mapping break down most often—requirements, test coverage, or deviation linking? Options: Requirements, Test coverage, Deviation linking, All three equally, Other
• Who creates the test scripts and who executes them in your process? Options: Validation team writes & executes, Validation writes, IT executes, IT writes & executes, Vendor provides scripts, Combination
• How often do deviations during testing cause scope creep or rework beyond planned effort? Options: Almost always, Often, Sometimes, Rarely
• Show me a concrete example: describe one protocol or artifact you consider strongest, and one you consider weakest, and why.

Vendor Docs, Silent Vendors, and Hidden Gaps

• How reliable are your vendors at providing the documentation you need (e.g., design specs, test evidence, CSV deliverables)? Options: Always timely & complete, Often timely with some gaps, Slow and incomplete, Unreliable/unresponsive
• Which vendor documents are most frequently missing or low-quality? Options: Design/architecture docs, Vendor test reports, Change logs/version history, User manuals, Validation-specific deliverables
• When vendor documentation is missing, how do you typically respond? Options: Delay validation, Create internal workarounds, Engage vendor escalation, Proceed with assumptions and note gaps
• How long does it usually take to resolve a vendor documentation gap once raised? Options: <1 week, 1–3 weeks, 3–8 weeks, >8 weeks, Variable/unknown
• Tell me about a time vendor documentation caused a failed or delayed test—what happened and what did you have to change?
• If vendor cooperation improved, what immediate effect would that have on your validation timelines or backlog?

Who Actually Signs Off When Things Get Messy?

• When a deviation or gap threatens release, who has the final sign-off authority to accept residual risk? Options: Quality Director/Head of QA, Validation Manager, IT Director, Cross-functional change control board, Other
• How clear are roles and responsibilities between Quality and IT during validation projects? Options: Very clear, Mostly clear with occasional overlap, Unclear and causes friction, Undefined
• Describe a recent cross-team conflict over validation scope—what was the disagreement and how was it resolved?
• Who in your organization is typically accountable for maintaining validation artefacts long-term (retention and change control)? Options: Quality/QA, IT, System Owner/Product Team, Shared responsibility, Other
• How effective are your current escalation paths when a project stalls—fast and decisive, slow but eventual, or inconsistent? Options: Fast and decisive, Slow but eventual, Inconsistent/depends on personalities, Non-existent
• If you could change one interpersonal or governance thing to speed validation, what would it be?

What Would Inspection-Ready Success Actually Look Like?

• Imagine the inspection is over and everything went well—what three things were visibly different about your validation program?
• Which measurable signals would prove a pilot delivered value for you? Options: Number of closed observations, Time-to-inspection-ready, Reduction in backlog, Fewer deviations during PQ, Improved audit scores
• How much reduction in lead time would you consider a successful pilot (percentage or days)? Options: 10–20%, 20–40%, 40–60%, 60%+, Prefer to specify days
• What level of documentation completeness do you need to feel comfortable with an inspection (e.g., full traceability, signed protocols, evidence attachments)? Options: Full traceability & signed evidence, Signed protocols with attachments, Partial evidence with plans to complete, Minimum required to respond to findings
• How would you like success communicated internally—single executive summary, detailed folder handover, or both? Options: Executive summary, Detailed handover package, Both, Other

What Could Break This Plan—Let’s Name the Risks Loudly

• What single risk do you fear most when starting a validation project: vendor delay, scope creep, regulatory change, or internal resource loss? Options: Vendor delay, Scope creep, Regulatory change, Resource loss, Other
• How often have unexpected configuration issues added weeks to your validation timeline in the past year? Options: Never, Once, 2–3 times, 4+ times
• When scope expands during testing, who decides whether to absorb the extra work or re-scope the effort? Options: Quality, IT, Change control board, Project sponsor, Noone/unclear
• How resilient is your timeline to losing 20% of planned validation effort due to higher-priority business work? Options: Still okay, Moderately impacted, Major delays likely, Timeline collapses
• Which contingency would you prefer if a vendor stalls: extend timeline, bring in third-party expertise, or reassign internal staff? Options: Extend timeline, Bring third-party expertise, Reassign internal staff, Switch vendor

Pilot Readiness: Could We Start Tomorrow?

• If we proposed a pilot for one system, which system would you pick and why?
• What are the non-negotiable acceptance criteria for a pilot to be considered successful? Options: Complete IQ/OQ/PQ with evidence, Closed deviations with CAPAs, Full traceability matrix, Formal sign-off by Quality, Other
• Which environments and access must be guaranteed before work begins (select all that apply)? Options: Test environment access, UAT environment, Vendor sandbox, Production-like data/sample, Admin-level support, Other
• What sample deliverables would make you confident to scale the approach—master plan template, completed protocol set, deviation log, or executive summary? Options: Master plan template, Completed IQ/OQ/PQ protocols, Deviation log and CAPAs, Executive summary & handover
• Realistically, how quickly could your team provide required inputs (owner contacts, access requests, vendor agreements) once a pilot is agreed? Options: Within 1 week, 1–2 weeks, 2–4 weeks, Longer than 4 weeks

Practical Constraints: Budget, Time, and Appetite for Change

• Do you have budget allocated for third-party validation assistance this quarter? Options: Yes — allocated, Yes — request pending, No — must reallocate, Unknown
• How would you prefer to engage with a validation partner: fixed-price pilot, time-and-materials, or milestone-based delivery? Options: Fixed-price pilot, Time-and-materials, Milestone-based, Hybrid
• What internal approvals would be required to sign a pilot SOW (roles/titles)?
• How much risk are you willing to accept in a pilot—tolerate some incomplete evidence to accelerate, or require full completeness before sign-off? Options: Tolerate some incompleteness, Require full completeness, Need case-by-case discussion, Unsure
• If the pilot demonstrated value, how quickly could you scale to additional systems (select best case)? Options: Immediately, Within 1–3 months, 3–6 months, Longer/Depends on budget

Communication, Governance, and Decision Rhythm

• How often do you want status updates during a pilot—daily standups, weekly summaries, or milestone updates only? Options: Daily standups, Twice-weekly, Weekly summaries, Milestone updates only
• Who should be on a weekly pilot steering call from your side (roles only)? Options: Quality/QA Lead, Validation Manager, IT/Infrastructure Lead, Product/System Owner, Procurement/Finance
• What format helps you make decisions fastest—concise executive summary, detailed evidence package, or annotated gap log? Options: Executive summary, Detailed evidence package, Annotated gap log, Combination
• When things go off track, how would you like escalation handled? Options: Immediate escalation to exec sponsor, Escalate through PMO, Resolve at working group then escalate, Other

Getting Comfortable Together

• Tell us the one‑sentence summary of the system or release you're preparing to validate and the target go‑live or inspection date.
• Who on your team is most impacted if the validation timeline slips, and how would that impact show up day‑to‑day?
• How urgent is this validation relative to other projects on your plate right now? Options: Critical — tied to release or inspection, High — impacts timelines, Medium — important but flexible, Low — nice to have
• How do you currently feel about starting deployment activities — confident, cautious, or stretched thin? Options: Very confident, Cautious, Stretched thin, Overwhelmed
• Have you partnered with an external validation firm before on a pilot? Tell us briefly what worked and what didn't.

Who Really Owns the Outcome?

• If the deployment fails to provide inspection‑ready evidence on time, who will be held accountable — and are you comfortable with that answer?
• Which role is the authoritative decision‑maker for changes to validation scope or acceptance criteria? Options: Quality Director, Validation Manager, IT Director, Project Manager, Vendor, Other
• List all individuals who must approve IQ/OQ/PQ artifacts before release (names and roles).
• Do you have a documented escalation path for cross‑functional blockers (e.g., quality → regulatory → executive)? Options: Yes — documented, Informal but known, No, Not sure
• How many people are available to execute test scripts during the scheduled windows? Options: 0, 1–2, 3–5, 6–10, 10+

Are Your Environments Truly Production‑Equivalent?

• How often have you discovered after validation that the 'test' environment behaved differently than production?
• Which environments will we need access to for this engagement? Options: Development, Integration / Staging, UAT, Performance / Load Test, Production (read‑only), Other
• Do the environments mirror production in configuration, version, customizations, and integrations? Options: Exactly the same, Mostly similar with minor differences, Significant differences, Unknown
• Who owns provisioning and access to each environment, and what lead time do they need to grant access?
• How frequently are environments refreshed from production configuration or data? Options: Daily, Weekly, Monthly, Quarterly, Rarely/Never, Unknown
• Are there scheduled IT maintenance windows or planned deployments during our proposed validation period? Options: Yes — dates known, Yes — dates TBD, No, Not sure

What Are Your Vendors Hiding (or Missing)?

• If a regulator asked for the vendor's validation deliverables tomorrow, would you be able to hand them over?
• Which vendor documents are already available for this system? Options: Vendor IQ/OQ, Vendor test scripts, System architecture diagram, Requirements traceability, Operational runbooks/user manuals, None/partial
• How cooperative are your vendors when asked to provide evidence or participate in assisted testing? Options: Very cooperative, Usually cooperative, Slow but responsive, Unresponsive, We control everything internally
• Are there contractual, IP, or licensing restrictions that prevent using vendor materials directly in your validation package? Options: Yes — restrictions exist, No, Don't know
• If vendor documentation gaps exist, who on the vendor side can close them and what is a realistic timeline?

Will Your Test Data Pass a Regulator's Scrutiny?

• Is any of your planned test data likely to trigger data privacy, PHI, or integrity concerns during inspection?
• What types of sample/test data will we use for IQ/OQ/PQ? Options: Synthetic/anonymized data, Production‑masked data, Full production data (rare), Subset of production, No data needed
• If using production‑derived test data, do you have documented masking, consent, or data‑minimization processes? Options: Yes — documented, Planned but not documented, No, Not applicable
• Who owns data extraction, masking, and loading into test environments, and how long does the process take?
• Are audit trails, electronic signatures, and retention settings configured and verifiable in the test environments? Options: Yes — fully configured, Partially configured, No, Unknown

Who Will Execute When the Clock Starts?

• If a critical deviation surfaces during IQ/OQ/PQ, who will stop their day and handle it immediately?
• Who is assigned as the primary test executor and the designated backup for each testing phase (IQ, OQ, PQ)?
• Are test scripts or protocols already assigned to named SMEs, or do assignments need to be made? Options: Yes — fully assigned, Partially assigned, Not yet assigned
• Do the named executors have up‑to‑date training records and CVs available for inspection? Options: Yes — up to date, Some are outdated, No, Unknown
• What contiguous calendar time can your SMEs commit during the execution window (e.g., full weeks, repeated half‑days)? Options: Full weeks, Several half‑days, One‑off sessions, Very limited, Unavailable

What Will Make Us Fail—or Prove We've Succeeded?

• What's the single hidden dependency that would derail this validation if it isn't resolved in the next two weeks?
• List your top three non‑negotiable acceptance criteria for the pilot validation (specific tests, traceability, deviation resolution expectations).
• Are there hard regulatory or business dates tied to this work (inspections, product release)? Options: Yes — fixed date, Yes — date window, No, Unknown
• What are the biggest known risks (e.g., vendor delays, environment mismatch, resource shortage) and what mitigation plans are already in place?
• On a scale of 1–10, how confident are you that an inspection‑ready package can be delivered within the current timeline? Options: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
• What would be the one early sign you want us to surface immediately if we see it during execution?

Quick Snapshot: Where Things Stand

• In one sentence, how would you describe the current status of this validation package? Options: On track, Near completion, Lagging, Stalled, Other
• Which system or application is this validation package for (product name/version)?
• What target date or trigger are you working toward (inspection date, go-live, release window)? Options: Confirmed inspection date, Planned go-live date, Rolling release window, No fixed date, Other
• Roughly how many test cases are currently open, failed, or pending review? Options: 0–10, 11–50, 51–200, 201–500, 500+
• Who are the three people we should talk to first about this package (name, role, best contact)?

If an Inspector Walked In Tomorrow, Would You Be Nervous?

• If an FDA investigator opened your validation binder right now, what single gap would make you most concerned?
• When was your last regulatory inspection or audit for a similar system? Options: Within 6 months, 6–12 months, 1–3 years, More than 3 years, Never
• Which topics would you expect an inspector to probe first in this package? Options: Requirements traceability, Deviation handling, Data integrity controls, Change control, Vendor documentation, Other
• How confident are you that current documentation meets 21 CFR Part 11 / Annex 11 expectations? Options: Very confident, Somewhat confident, Unsure, Not confident
• What past inspection finding (if any) most influences how you prepare this package?

Who Actually Owns Each Piece?

• Where do ownership gaps most often slow validation closure—validation team, IT, vendor, or quality review? Options: Validation team, IT/Infrastructure, Vendor/supplier, Quality assurance, Cross-functional handoff
• Who owns the Validation Master Plan, and do we have the approved version on file? Options: Quality (VMP owner), Validation lead, IT owner, Vendor provided, Not assigned
• For IQ, OQ, PQ and the trace matrix—please list the current named owners and approvers (role + name if possible).
• Are access, test environments, and necessary credentials confirmed and documented before testing? Options: All confirmed, Partially confirmed, Planned but not confirmed, Not confirmed
• If vendor documentation is incomplete, what are the top missing items (e.g., architecture diagram, installation guide, risk assessments)?

Are Your Tests Truly Telling the Story?

• Do your test scripts map directly to a specific requirement or risk—yes, partially, or no? Options: Mapped 1:1 to requirements, Partially mapped, Many tests not mapped, Mapping is unclear
• Where is your requirements traceability matrix stored, and is it up to date? Options: GxP QA repository, Validation management tool, Shared drive, Not maintained, Other
• Approximately how many requirements are in-scope and how many test cases do you have (give ranges)? Options: <50 reqs / <200 tests, 50–150 reqs / 200–500 tests, 150–500 reqs / 500–2000 tests, Other
• What percentage of executed tests are currently passing without deviations? Options: >95%, 85–95%, 70–84%, <70%, Unknown
• Give an example of a test or requirement that feels weak or non-evidentiary—what would you change to make it inspection-ready?

When Tests Fail — Are You Ready to Close the Loop?

• When a test produces a failure, is your deviation workflow consistently: document → investigate → disposition → verify? Options: Consistent, Often skipped steps, Inconsistent, Ad-hoc
• How many open deviations related to testing or validation remain in the backlog? Options: 0–5, 6–20, 21–50, 51+
• What is the average time from deviation discovery to formal closure (days)? Options: <7 days, 7–30 days, 31–90 days, >90 days, Unknown
• Who performs root cause analysis and who approves corrective actions (role names)?
• Are deviations linked to CAPAs and change control actions in your records? Options: Yes, linked and traceable, Partially linked, Not consistently linked, No linkage

Can You Reconstruct Everything in Minutes?

• Could you, right now, produce a single document that traces a high-risk requirement from URS through test evidence to release in under 30 minutes? Options: Yes, easily, Yes, with effort, No, needs assembly, No, not possible
• Where are your traceability artifacts kept (pick all that apply)? Options: Validation management tool (e.g., Vera/ValGenesis), Quality document system (QMS), Shared drive, Spreadsheet/locally maintained, Vendor portal, Other
• Do your test records contain time-stamped evidence, tester identity, and electronic signature where required? Options: All records have required evidence, Most records do, Many records missing items, Records lack signatures/timestamps
• Describe one recent instance where reconstructing a trace took longer than expected—what failed and why?
• How do you version-control artifacts (master doc with change history, tool-managed versions, manual file naming)? Options: Tool-managed versioning, Master doc with change history, Manual naming conventions, No formal version control

The Package: Would It Read Clearly to an Inspector?

• If an inspector opened your final package, would they understand intended use, test strategy, and conclusions within 10 minutes? Options: Yes, With brief guidance, No
• Do you have an index/cover page and a one-page executive summary that links to acceptance decisions? Options: Executive summary + index present, Index present only, Summary only, Neither present
• Which documents are currently missing or incomplete (select all that apply)? Options: Validation Master Plan, User Requirements (URS), Risk Assessment, IQ, OQ, PQ, Traceability matrix, Deviations/CAPA records, Vendor documentation, Training records, Other
• Are acceptance criteria for the pilot clearly documented and signed off (MVP vs full package)? Options: Clearly documented and signed, Documented but unsigned, Not documented, Unclear
• Where will the final, inspection-ready package be archived and who will own retrieval during an audit? Options: QMS archive, Validation tool, Shared drive with controlled access, Vendor repository, Not decided

Next Steps & Escalation: Who Gets the Call When Things Go Wrong?

• If a high-risk deviation jeopardizes your inspection or release date, who is authorized to escalate and make the final go/no-go decision?
• Do you have predefined escalation paths and SLA targets tied to inspection milestones? Options: Yes, documented SLAs, Informal escalation process, No formal escalation path, Working on it
• What contingency actions are acceptable if vendor deliverables are delayed (extend timeline, reduce scope, escalate contractually)? Options: Extend timeline, Reduce scope (MVP), Escalate to vendor management, Engage alternate vendor/resource, Other
• Which readiness gates must be satisfied before we start final compilation (select all that must be complete)? Options: All tests executed, All deviations closed, Traceability complete, Executive sign-off, Vendor docs received, Environment access confirmed
• What single action, completed in the next week, would most reduce your risk of a last-minute finding?