Who’s Actually in the Room — Start Fast

• Who will be our primary point of contact for this tapeout (name, role, and best contact method)?
• Which team members will be actively involved during the 8-week readiness window? Options: VP of Engineering, Design Director, Physical Design Lead, Tapeout Engineer, Project Manager, Foundry Liaison, RTL Owner, Other
• Do you currently have a dedicated tapeout engineer assigned to this project? Options: Yes — internal full-time, Yes — contractor/part-time, No — not assigned, Hiring/in process
• Which roles must sign off before we submit to the foundry? Options: VP of Engineering, Design Director, Physical Design Lead, Quality/Signoff Owner, Foundry Account Rep, Legal/Compliance, Other
• For each approver above, briefly list their top acceptance concern (e.g., timing slack, DRC count, IP golden data availability).

If I told you this tapeout could be rejected on day one, what would surprise you?

• From your viewpoint today, what percent of final signoff work is complete (rough estimate)? Options: 0–20%, 21–40%, 41–60%, 61–80%, 81–100%
• Please list current open counts or ranges for: DRC violations, unresolved timing paths, and missing fill instances.
• Do you have legacy IP blocks with incomplete signoff history or missing golden data that could surface late? Options: Yes — multiple blocks, Yes — 1–2 blocks, No known legacy issues, Unsure / need to audit
• If legacy IP issues exist, how long have those gaps been on your backlog? Options: >18 months, <1 month, 1–6 months, 6–18 months, Unknown
• Which current technical item keeps you up at night entering the 8-week window, and why?

Who truly holds the 'no-go' veto?

• Who in your organization can unilaterally delay or stop the tapeout, and what criteria do they use to make that call?
• How do those decision-makers weigh risk—by technical metrics, schedule impact, potential revenue loss, or customer commitments? Options: Technical metrics (DRC/timing), Schedule impact, Cost/respin risk, Customer launch date, Other
• For each veto-holder, what threshold of remaining DRCs or timing violations would typically trigger a stop decision?
• How often do your approvers convene during final signoff, and what artifacts do they expect at each meeting? Options: Daily standup, Multiple times weekly, Weekly, Ad hoc as issues arise
• How would you prefer critical escalations be presented to those stakeholders (dashboard link, one-page exec summary, live review session)? Options: Real-time dashboard, One-page executive summary, Live demo/review, Email + highlights

Your Foundry’s Unwritten Rules — Tell Us the Secrets

• Which foundry are you targeting for this submission? Options: TSMC, Samsung Foundry, GlobalFoundries, UMC, SMIC, Other
• What is the target process node and PDK/version for this tapeout (e.g., N5 vX, 28nm vY)?
• Have you submitted to this foundry/node before? If so, how many tapeouts and with what outcomes? Options: 0, 1, 2–4, 5+
• Are there known foundry-specific, undocumented checks we should be aware of (e.g., metal density gradients, via redundancy, custom antenna rules)? Options: Yes — documented to us, Likely — undocumented, No — none known, Unsure
• If you’ve encountered undocumented foundry requirements before, what failed and how was it resolved?
• Who is your foundry account representative and how would you rate their responsiveness during final signoff? Options: Very responsive, Generally responsive, Slow, Unreliable, No direct contact

What Counts as First-pass Victory — Be Brutally Specific

• List the exact acceptance criteria you expect the foundry to require for first-pass acceptance (be as numeric and specific as possible).
• Which of these criteria are absolutely non-negotiable versus conditionally negotiable? Options: DRC clean/threshold, Timing worst negative slack, Total unresolved timing paths, Fill density targets, LVS clean, PVR/Power/IR thresholds, Reticle/MASK prep complete, Other
• For any negotiable items, what remediation windows and cost tolerances would you accept (e.g., 1-week patch, paid respin vs. reject)? Options: Minor fixes <1 week, Post-submission patch acceptable, Respin only if cost < $X, Respin unacceptable
• Who on your team will formally sign the first-pass acceptance and what evidence will they require? Options: VP Engineering, Design Director, Physical Design Lead, Quality/Signoff Owner, Other
• If we meet these acceptance criteria, how would your confidence change about launch readiness (qualitative description)? Options: Completely confident, Mostly confident with minor caveats, Some remaining concerns, Not confident

Where the Clock Hurts Most

• If the tapeout schedule slips by one week, what are the most serious downstream impacts (revenue, customer commitments, mask cost)?
• What is the absolute drop-dead tapeout submission date and are there upstream hard-cutoff milestones we should know now?
• How much room do you have for last-minute RTL/ECO changes in the final 2 weeks before submission? Options: Major changes OK, Only small ECOs allowed, Freeze — no changes, Depends on block
• What contingency resources are available if we need rapid remediation (extra engineering hours, contingency budget, mask respin fund)? Options: Extra engineering hours, Contingency budget, Mask respin fund, No contingency
• When time is scarce, what trade-offs would you accept (e.g., defer non-critical features, accept small DRCs with known remediation plan)?

How We’ll Work Together in Week One — Your Ideal Integration

• What must happen in week one for our PM and engineers to be considered successfully integrated into your EDA workflow?
• Which EDA tools and specific tool versions do we need to be active in during the engagement? Options: Calibre, Hercules, Synopsys ICC2/PrimeTime, Cadence Virtuoso/Assura, Mentor Graphics, Other
• What level of database access will you permit our engineers (full access, masked views, read-only, remote access only)? Options: Full access, Masked views, Read-only, Remote access only, Other
• How do you prefer we deliver status: a daily live dashboard, 15-minute standup, weekly exec brief, or a combination? Options: Daily dashboard, Daily standup, Weekly executive brief, Combination
• What security, NDA, or foundry gating steps must we complete before any access is granted?
• Who is the escalation contact for PM issues and how should we reach them outside standard hours? Options: Email, Phone/SMS, Slack/Teams, Pager, Other

Proof, Trust, and References — Show Me the Receipts

• What specific evidence or references would make you comfortable choosing a tapeout partner for this project? Options: Foundry-specific tapeout count, Process-node experience, Client references (same design size), Live dashboard demo, Week-one PM integration examples, Other
• How many comparable references (same foundry/node/design complexity) would you like to speak with before deciding? Options: 0, 1, 2–3, 4+
• What three questions will you ask references about their vendor experience?
• Would you find a live demo of our violation-tracking dashboard connected to a sanitized version of your DB helpful in week one? Options: Yes — strongly, Maybe — schedule dependent, No
• What contractual guarantees or SLAs (if any) would materially increase your confidence in a first-pass acceptance outcome?

Decision Time — What Would Make You Say Yes Today?

• Based on everything we've discussed, what is the single most important outcome we must commit to for you to proceed now?
• What conditions must be satisfied in week one to keep the engagement moving forward (select all that apply)? Options: Access granted to DB, Initial snapshot + violation report delivered, PM embedded in workflow, Foundry acceptance criteria confirmed, Initial remediation plan created
• Who needs to approve commercial terms on your side and what procurement timeline should we expect? Options: VP Engineering, Procurement, Legal, CFO/Finance, Other
• Are there budget approvals or procurement constraints that could delay onboarding? If yes, please describe briefly.
• Which onboarding format would help you decide fastest: one-page RACI, week-one checklist, Gantt timeline, or live kickoff walk-through? Options: One-page RACI, Week-one checklist, Gantt timeline, Live kickoff walk-through, Combination

Quick Snapshot — Where's the database right now?

• Which foundry and process node will receive this submission? Options: TSMC N5/N5P, TSMC N7/N7P, GlobalFoundries 14nm/12nm, Samsung 5nm/7nm, SMIC nodes, Other
• Roughly how many open DRC violations exist today (select best range)? Options: <100, 100–499, 500–1,999, 2,000–4,999, 5,000+
• How many unresolved timing paths remain (critical / setup / hold) — choose the best bracket? Options: 0, 1–9, 10–49, 50–199, 200+
• Estimate the percentage of the design missing required fill patterns or density fixes. Options: 0%, 1–9%, 10–24%, 25–49%, 50%+
• What EDA tools and versions are you using for signoff (place a comma-separated list if multiple)?
• When was your last full signoff run (DRC/LVS/PEX/timing)? Options: Within 24 hours, Last 3 days, Last 2 weeks, Last month, Over a month ago
• Who is currently the owner for tapeout closure activities on your side? (name, role, and availability)

If we sent your database to the foundry tomorrow, what would they likely flag?

• What single issue are you most worried will cause a first-pass rejection? Options: DRC density/fill, Antenna/EM violations, LVS mismatches, Timing violations, Mask data/reticle prep, Other
• Which DRC rule classes currently have the highest counts or the most stubborn violations? Options: Metal spacing, Via redundancy, Density/metal fill, Minimum enclosures, Antenna rules, Other
• Have you had previous first-pass rejections at this foundry or node? If yes, how many and for what reasons? Options: No prior rejections, 1 rejection, 2 rejections, 3+ rejections
• On a scale from 1–10, how confident are you that the current database will meet first-pass acceptance? Please explain the main reason for your rating. Options: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
• Give one concrete example of a hidden or undocumented foundry expectation that has tripped you up in the past (or that you're worried about now).

Where are the unknowns hiding — the things you can’t easily see yet?

• How would you describe the risk coming from legacy or third‑party IP blocks in this design? Options: Low—well-validated, Medium—some gaps, High—unknown integration issues, Unsure
• Which of these IP-related gaps exist today? Options: Missing abstracts/symbols, Outdated IP PDK versions, No active owner/contact, Unverified fill/density compliance, None of the above
• List the IP blocks you suspect could create late surprises (block name + brief reason).
• How long have these IP uncertainties persisted (weeks/months/years)? Options: <1 week, 1–4 weeks, 1–3 months, 3–12 months, 1+ year
• If a legacy IP block requires a respin-level fix, what is your tolerance for timetable slippage (days/weeks) and cost? Options: Acceptable up to 1 week / <$50k, 1–3 weeks / $50–$150k, 3–6 weeks / $150–$300k, Not acceptable / would trigger program review

What would a foundry rejection look like — and could we spot it earlier?

• Which acceptance checks has your team already completed against the foundry checklist? Options: DRC full run, LVS full run, PVR/EM checks, Reticle/mask prep, None yet
• Have you run the foundry’s formal first-pass checklist or only internal signoffs? Options: Formal foundry checklist completed, Partially completed, Only internal checks, Not sure/need help
• Are PVR (process variability) and model corner signoffs available for review? If not, which are missing? Options: All available, Corner PVR missing, Models incomplete, Not performed
• What mask-data/mask-prep tasks are outstanding (e.g., OPC checks, reticle layout prep, E-beam shot count)?
• What evidence would you want to see from us to feel confident the foundry will accept first pass? Options: Daily DRC/LVS dashboards, Signed off checklist per foundry item, Per-block remediation plan, Reference tapeout history at foundry/node, Other

How fast can we actually close the backlog if we go all-in?

• If we cleared the highest-priority rules first, how many engineers (internal + external) could be assigned to fixes concurrently? Options: 1–2, 3–5, 6–10, 10+
• What’s your realistic per‑day closure rate for violations under focused effort (violations/day)? Options: <10, 10–49, 50–199, 200+
• Which types of violations historically take the longest to resolve for your team (pick top two)? Options: Metal density/fill, Timing netlist/timing paths, LVS mismatches, Antenna fixes, Complex IP integration
• What turnaround SLAs would make you comfortable (e.g., highest-risk fixes closed within X days)? Options: 24–48 hours, 3–5 days, 1–2 weeks, Depends on issue
• Describe any constraints that slow fixes (tool licenses, compute, IP owner availability, legal access, etc.).

What are you secretly worried might slip through — and how bad would that be?

• Which of these outcomes would cause the most damage to your program? Options: Mask respin (cost/time), Yield loss after fab, Delayed product launch, Customer contract penalties, Reputational damage
• If a respin occurs, what is your estimated incremental cost impact? Options: <$50k, $50k–$150k, $150k–$300k, >$300k, Unsure
• Beyond dollars, what non-financial consequences worry you most (hint: deadlines, partners, stock, customer commitments)?
• How do you currently define acceptable risk for this tapeout (e.g., zero‑tolerance on certain classes, flexible on others)? Options: Zero tolerance for any first-pass DRC failures, Zero tolerance for certain classes only, Accept small cosmetic failures, Undefined
• Who in your organization must sign off before you accept a foundry handoff (roles, not names)?

How would you like to see progress — and who needs to see it?

• What reporting cadence gives you the right confidence: daily, twice-daily, weekly, or ad-hoc? Options: Daily dashboard, Twice-daily, Weekly summary, Ad-hoc on milestones
• Which metrics do you want on a live dashboard (pick up to four)? Options: Total open DRC by class, Open timing paths by severity, Per-owner open counts, Blocked IP items, Mask-prep readiness, Predicted first-pass risk score
• Who should have read-access vs. edit/owner access to the dashboard (list roles)? Options: VP Engineering, Design Director, Tapeout PM, Foundry Liaison, Engineering Leads, Other
• Which collaboration channels do you prefer for daily updates and escalations? Options: Slack/MS Teams, Email with attachments, Direct SFTP drops + summary, PM tool (JIRA/Asana), Other
• Are there compliance or security controls we must follow to access your database (e.g., VPN, IP whitelisting, specific NDA terms)?

What must be true for first‑pass acceptance to feel like success?

• Choose the minimum set of outcomes you require for us to call it a successful first‑pass submission. Options: Zero critical DRC failures, Foundry acknowledgment of completeness, Signed internal signoff from design owner, Mask-data ready for handoff, Traceable evidence for each closed violation
• Are there any foundry acceptance items you consider non-negotiable (list them)?
• Would you accept a conditional handoff (e.g., hand off with low-risk cosmetic exceptions) or only a complete clean first pass? Options: Only complete clean first pass, Conditional with documented exceptions, Depends on exception types
• Which stakeholders must be satisfied at the moment of handoff (internal and external)?
• How should we demonstrate evidence for each closed item (screenshots, runlogs, commit hashes, foundry checklist entries)? Options: Runlogs & reports, Annotated screenshots, Committed signoff artifacts, All of the above, Other

Immediate access and next steps — what do we need to get started now?

• Do we have permission to run a full, read-only tapeout snapshot on your database for an independent assessment? Options: Yes—access available now, Yes—need to schedule, No—not yet, Need legal/NDAs first
• Which transfer method do you prefer for secure data handoff? Options: SFTP (SSH), Encrypted cloud share (AWS/GCP/Azure), Physical drive under NDAs, Vendor portal
• What credentials/licenses will we need to run signoff tools in your environment (list tools and license arrangements)?
• Are there calendar constraints in the next two weeks we should avoid (frozen windows, holidays, exec reviews)? Options: No constraints, Specific freeze windows—provide dates, Upcoming holiday(s)
• Who is the single point of contact for rapid decision escalations during the assessment?

Quick Check — The Essentials We Need First

• What is your firm’s target tapeout date (YYYY-MM-DD)?
• Which foundry and process node is this submission targeting? Options: TSMC 5nm, TSMC 7nm, TSMC 16/12nm, Intel Foundry, GF 7nm/12nm, SMIC nodes, Other
• How large is the design (tapeout GDS size, layers of routing, or mm^2)?
• Roughly how many open DRC violations and failing timing paths do you currently have? Options: <100, 100–500, 501–1,500, 1,501–3,000, >3,000, Unknown
• Do you have a dedicated tapeout or signoff engineer on staff for this project? Options: Yes — full time, Yes — part time/shared, No — relying on design leads, No — hiring/contractor planned
• Who should our team contact first (name, role, email, preferred channel)?

If the Mask Respins — How Bad Would It Be?

• What would a mask respin cost your program in dollars, schedule, customer deliverables, and team morale?
• Which downstream commitments (customers, product launches, revenue milestones) are tied to this tapeout window?
• Has your leadership set explicit tolerance levels for first-pass foundry acceptance (e.g., zero critical DRC, less than X fill violations)? Options: Yes — detailed criteria exist, Yes — high-level targets only, No — not defined, Unsure
• How would a one-week delay change your product roadmap or go-to-market plan? Options: Severe impact, Moderate impact, Manageable, Minor
• Tell us about the last time you had a tapeout issue: what went wrong, what surprised you, and how long did it take to recover?

Who's Driving the Final Mile — Roles, Authority, Pain

• Why hasn’t a single owner been empowered to make the final tapeout decisions today?
• List the current owners for database signoff, mask data prep, foundry liaison, and PM (name + role).
• Which of these roles has formal escalation authority to approve a waiver or request a respin? Options: VP Engineering, Design Director, Tapeout Owner, Foundry Liaison, Other, No defined authority
• How available will your signoff owners be during the 8-week window (daily, on-call, limited, blocker)? Options: Fully available (daily), Mostly available (frequent reviews), Limited (as-needed), Unavailable during critical weeks
• Do you currently use a formal change-control process for last-minute fixes (check-in, signoff, rollback)? If yes, describe briefly. Options: Yes — enforced tool-based workflow, Yes — informal email approvals, No formal process, Planning to set one up

Will the Foundry Receive a Usable Submission?

• What's the single most likely reason the foundry would reject your submission on first pass?
• What file formats and delivery methods does your foundry expect for mask data and signoff artifacts? Options: GDSII + OASIS, Reticle prep files, Stream-out via SFTP, Foundry portal upload, Other
• Are final PVR/DRC/DFM decks and foundry-specific runlists up-to-date and validated for your node? Options: Fully validated and current, Mostly current — small gaps, Outdated or incomplete, Unknown
• Do you have a single canonical database for the final handoff, or multiple diverging branches? Options: Single canonical DB, Multiple branches merged regularly, Multiple branches with unresolved merges, We use snapshots only
• Where are your recent verification logs and evidence stored, and can we access them immediately? Options: Central repo with access, Central repo but restricted, Scattered across team laptops, Not available

Do We Actually Have the Tools and Keys Ready?

• Which critical EDA and foundry tools are people currently blocked from accessing right now? Options: Calibre, HERCULES, PrimeTime, ICC/ICC2, StarRC, Foundry portal, Licenses all accessible, Other
• Are license counts and runtimes sufficient to run peak-night verification loads (e.g., parallel Calibre runs)? Options: Sufficient, Tight but manageable, Insufficient — risk of queueing, Unknown
• Do we have secure transfer mechanisms and keys set up for large file handoffs (SFTP, Aspera, internal DLT)? Options: Yes — tested, Yes — untested, Planned but not set up, No
• Is there a mirrored compute environment (cloud or on-prem) we can use to run verification under your configs? Options: Exact mirror exists, Partial mirror, No mirror — must set up, Unsure
• If we need additional tool access, who approves license requests and how quickly can those approvals be granted?

Which IP Blocks Could Upset the Plan?

• Which legacy or third-party IP blocks are most likely to surface unknown DRC/fill/timing issues during final signoff?
• For each high-risk IP block, do you have a designated owner and vendor contact with a support SLA? Options: Yes — owner + SLA, Owner only, Vendor contact only, No owner or vendor SLA
• Are there known license, NDA, or escrow constraints that could prevent us from modifying or re-flattening an IP block? Options: Yes — restrictions apply, Some restrictions but workable, No restrictions, Unsure
• Have any IP blocks been carved out of verification runs or handled separately in past signoffs? Options: Yes — separated and documented, Yes — separated but not documented, No — always integrated, Not applicable
• What would you need from us to assume ownership of IP remediation (vendor liaison, code changes, re-qualification)? Options: Code changes + test, Vendor management, Design-team pairing, Only advisory support, Other

If the Clock Strikes Midnight — Contingency Thinking

• If a critical violation cannot be closed within your window, what’s your preferred fallback — delay, waiver request, localized redesign, or respin? Options: Delay tapeout, Request foundry waiver, Local redesign to avoid violation, Plan for respin, Other
• What is the decision threshold that triggers invoking your contingency plan (e.g., >X critical DRC, >Y timing fails)?
• Who has sign-off authority to execute the contingency, and how quickly can they convene?
• What budget or reserve do you have available for emergency fixes, mask respins, or extended run-time? Options: Sufficient reserve, Limited reserve, No reserve — must escalate, Unknown
• How do you want us to surface high-risk items—automated alert, immediate call, or scheduled checkpoint? Options: Immediate call + escalation, Automated alert (email/Slack), Daily summarized report, Weekly only

How Transparent Should Progress Be?

• Why would daily violation-tracking dashboards change outcomes compared to your current status reporting?
• Who needs to see the dashboards and at what cadence (VP, Design Leads, Foundry Liaison, External partners)? Options: VP Engineering, Design Director, Tapeout Owner, Foundry Liaison, External Stakeholders, All of the above
• Which metrics matter most for your leaders (open DRC count, critical timing paths, fill shortfalls, PVR pass rate)? Options: Open DRC count, Critical timing paths, Fill coverage, PVR pass rate, Mask data readiness, Other
• Do you prefer our dashboard integrated into your existing PM tool (Jira/Confluence/Teams) or a separate portal? Options: Integrate into existing tools, Provide separate portal, Both, Undecided
• What escalation cadence would put you at ease (real-time alerts, daily morning syncs, weekly executive summaries)? Options: Real-time alerts, Daily syncs, Twice-weekly, Weekly summary, Other

Week One — How We Become Part of Your Team Fast

• What must happen in the first seven days for our PM and engineers to be fully productive on your project?
• Do we have a confirmed week-one access checklist (tool accounts, repo access, build scripts, runlists)? Options: Yes — checklist exists, Partially defined, No checklist, Planning to create one
• Which communication rituals should we adopt immediately (daily stand-up time, handoff window, weekly steering meeting)? Options: Daily stand-up, Twice-weekly technical sync, Weekly steering, Ad-hoc as needed, Other
• Who will be our single day-to-day point of contact and backup for operational queries?
• How should we measure our week-one success (access granted, first verification batch run, initial reduction in DRC counts)? Options: All access granted, First verification batch completed, Initial DRC reduction observed, PM integrated into workflow, Other

Commercial & Governance — The Commit That Lets Us Move Fast

• What commercial or contracting items must be settled before work begins (SOW, NDAs, SLAs, payment milestones)? Options: SOW, NDA, SLA/penalties, Payment milestones, PO, Other
• If we propose a week-one integration plan, what internal approvals are needed and how long do they typically take? Options: Immediate, 1–3 days, 4–7 days, Longer than a week
• What governance cadence do you expect for decisions during the 8-week window (daily ops, biweekly steering, ad-hoc exec)? Options: Daily ops + weekly steering, Daily ops only, Biweekly steering, Ad-hoc
• Are there reference checks or foundry-specific track record items you require from our team before committing? Options: Foundry-specific track record, Customer references, Case studies, None required, Other
• What would cause you to pause or delay a mutual commitment on the commercial terms?

Deciding Now — What Would Make You Hesitate?

• What is the single biggest unresolved concern that would make you hesitate to give us authorization to proceed today?
• If we addressed that concern within 48 hours, would you be willing to onboard our PM and engineers immediately? Options: Yes — immediately, Yes — after quick review, Maybe — need more info, No
• What additional proof points or guarantees would give your VP of Engineering the confidence to move forward (SLA language, milestone payments, escrow)?
• How should we document and agree on the initial success signals for first-pass foundry acceptance? Options: Formal signoff checklist, Mutual dashboard targets, Weekly acceptance review, Other
• Finally — what’s the best time for a short alignment call to convert this discovery into an immediate week-one action plan? Options: Today, Tomorrow, Within 48 hours, Next week, Other

Start Here — Quick Snapshot

• What is your target tapeout date (best estimate)? Options: Within 2 weeks, 2–4 weeks, 4–8 weeks, 8–12 weeks, More than 12 weeks, TBD
• Which foundry are you planning to submit to? Options: TSMC, Samsung Foundry, GlobalFoundries, UMC, SMIC, Other
• What process node / nominal PDK node are you targeting? Options: 90–40 nm, 28–16 nm, 10–7 nm, 5 nm and below, Analog/Custom node, Other / hybrid
• Roughly how many open DRC violations does your current database show? Options: 0–50, 51–250, 251–1,000, 1,001–2,500, 2,501–10,000, More than 10,000, Unknown / I need help checking
• Do you have a dedicated tapeout engineer or team currently focused on signoff? Options: Yes — full-time in-house, Yes — contractor(s) on short-term support, Partial coverage (shared engineers), No dedicated resource today
• Who is our primary contact for this conversation (role/title)? Options: VP Engineering, Design Director, Tapeout/Signoff Engineer, Program/Project Manager, Head of Manufacturing/MPW, Other

What Keeps You Up at Night?

• If we miss a single foundry acceptance rule, how confident are you that it won’t cost a mask respin or schedule slip? Options: Very confident — low chance of respin, Somewhat confident — manageable risk, Not confident — high chance of costly respin, Unsure
• Tell us about a past close-call or rejection—what happened, and what burned the most time or money?
• Which of these outcomes worries your leadership the most right now? Options: Mask respin cost, Missed tapeout date, Foundry rejection after submission, Late discovery of legacy IP violations, Damage to customer relationships / reputation
• How does the thought of a late-stage violation or respin affect the team emotionally and operationally?
• How tolerant is leadership for schedule slippage or added cost at this stage? Options: Zero tolerance — must hit date, Some tolerance with justification, Flexible depending on risk trade-offs, Undetermined / depends on execs

The Database Speaks — What Is It Telling Us?

• If your database could tell us one hidden problem that will cause a foundry rejection, what do you think it would say?
• Please break down current unresolved issues—select all that apply and estimate counts where possible. Options: DRC violations (by range) — see below, Timing violations/unresolved paths, Missing or incomplete fill density, Antenna/metal density edge cases, Legacy IP layout issues, Other (describe)
• If you selected DRC violations above, choose the best range that matches your database now. Options: 0–50, 51–250, 251–1,000, 1,001–2,500, 2,501–10,000, More than 10,000, Unknown
• How many timing paths are unresolved or marginal (rough estimate)? Options: 0–10, 11–50, 51–250, 251–1,000, Unknown / needs analysis
• Do you have automated fill insertion configured now, and does it run end-to-end in your flow? Options: Yes — fully automated and validated, Partially automated — manual steps remain, No — handled late or ad hoc, Uncertain / need us to check
• Are there known legacy IP blocks (third‑party or internal) that historically surface new violations late in signoff? Options: Yes — multiple blocks, Yes — one critical block, No known legacy surprises, Unknown / need inventory help
• Describe the last time you ran final PVR/DRC — what were the top three failures and how long did they take to resolve?

Who Decides—and Who Can't Be Surprised?

• Who will sign final acceptance to ship the database to the foundry, and are there hidden approvers we should know about?
• Which stakeholders must be kept in the loop daily versus weekly (pick all that apply)? Options: VP Engineering, Design Director, Tapeout Engineer, Systems Architect, Product Manager, Foundry Liaison, Legal/Compliance
• What are the non-negotiable acceptance criteria your team requires before giving 'go' for submission? Options: Zero DRC violations, Timing closure to defined margin, Fill density within spec, Signoff sign‑offs from IP owners, Mask data validation complete, Other — specify
• Who is your primary foundry contact for acceptance questions (name/team), and are they available for a joint walkthrough in week one? Options: Yes — named contact available, Yes — foundry team available but not assigned, No — we need foundry contact support, Unknown
• How do you prefer escalations to be handled if a critical issue appears—formal change control, direct exec notification, or tactical hotfix flow? Options: Formal change control with approvals, Direct exec/stakeholder notification, Tactical engineering hotfix with retroactive documentation, Hybrid — depends on issue severity
• Who owns the IP block signoffs and do those owners have bandwidth in the tapeout window? Options: IP owners are assigned and available, Assigned but bandwidth constrained, Unassigned — needs identification, Third-party IP — need vendor contact

If the Foundry Rejected Us Tomorrow, What Would That Cost?

• Imagine the foundry rejects the first submission — what is the realistic financial impact you expect? Options: <$50k, $50k–$150k, $150k–$300k, $300k–$1M, >$1M, Unsure
• Beyond direct cost, what operational or business impacts would a rejection create (pick all that apply)? Options: Customer SLAs missed, Revenue delay, Team burnout / attrition, Supplier / foundry relationship strain, Regulatory or qualification setbacks, Other
• What level of risk (probability × impact) would you accept for first-pass submission versus postponing to eliminate uncertainty? Options: Accept only near-zero risk, Accept small risk with contingency, Willing to accept moderate risk to keep date, High risk acceptable to avoid delay
• If we estimate a likely respin cost, who in your organization would approve that remediation spend? Options: VP Engineering / Exec, Program Manager, Finance, Cross‑functional approval required, Undecided / depends on amount
• Have you modeled contingency budgets or time buffers for a potential respin? If yes, please summarize.

What Would First‑Pass Acceptance Really Look Like?

• If you woke up on submission day and felt totally confident, what three metrics would be green on your dashboard? Options: DRC violations = 0, Timing slack margins met, Fill density compliant, Mask data validated (MRC/PVR), IP owner approvals complete, Other — specify
• What evidence or artifacts does your team require archived with the submission (pick all that apply)? Options: Final DRC report, Timing signoff summary, Fill reports and scripts, Mask prep checklist, Foundry pre-check correspondence, PM weekly dashboard export
• How often do you want visibility while we close items—daily dashboards, twice-daily syncs, or weekly summaries? Options: Real-time dashboard + daily summary, Daily dashboard + ad-hoc calls, Twice-weekly updates, Weekly progress report only
• Which format helps your execs make quick decisions—visual violation tracker, short status digest, or phone brief? Options: Visual violation tracker (dashboard), Short written status digest, Phone/VC brief with PM, Combination
• What would be an unacceptable surprise to find in the 'evidence' package after submission? Options: Missing DRC report, Incomplete timing signoff, No IP approvals, Mask data inconsistency, No contingency plan
• Are there specific foundry acceptance items that, if unmet, automatically trigger a delay in your release process? Options: Yes — list below, No — we accept fixes post-submission, Depends on the item

Week One — What Must Happen for Us to Move Fast?

• If our PM and engineers joined your team on Monday, what would be the top three things they must have by day two?
• Which EDA tools and versions are in your signoff flow (pick all that apply)? Options: Cadence Innovus/Tempus, Synopsys IC Validator/PrimeTime, Mentor Calibre, Custom scripts / in-house tools, Other — specify
• Do we have read/write access to the database and the automated scripts we need to run verification in your environment? Options: Unsure, Yes — full access granted, Partial access — some datasets restricted, No — access needs provisioning
• Who will be our day‑to‑day engineering liaison, and do they have protected time for tapeout activities? Options: Named liaison with protected time, Named liaison but with limited availability, No liaison assigned yet, Multiple liaisons — please specify
• What are your preferred acceptance checkpoints in week one (pick up to three)? Options: Initial DRC sweep and report, Timing quick-check paths, Fill insertion health check, Foundry pre-check alignment, PM onboarding and dashboard setup
• What integration risks do you anticipate in week one that could slow velocity (access, licensing, IP escrow, etc.)?

Who Do You Need to Hear From to Say Yes?

• Which references or proof points would reassure you most about our ability to get first-pass acceptance at your foundry/node? Options: Past tapeouts at same foundry/node, Customer references of similar design size, PM integrated with customer EDA workflow, Published case studies, Live demo of our violation dashboard
• If we offered a short joint readiness assessment, what would you need to see in its results to commit to a full engagement? Options: Clear DRC count reduction plan, Realistic time-to-green estimate, Prioritized remediation list with owners, Foundry-specific acceptance checklist validated
• Who on your side will run a reference check or request case studies, and what criteria will they use? Options: Engineering leadership, Procurement, Program manager, Other
• Which success stories (foundry + node + design scale) would you like us to share up front?
• How quickly would you need references returned to feel comfortable moving forward? Options: Within 24 hours, 1–3 business days, Within a week, No rush