Quick Snapshot: Who’s in the Room?

• Which best describes your role today? Options: Transmission Planning Manager, NERC Compliance Officer, VP/Head of Engineering, Study Manager/Coordinator, Lead Modeler/Analyst, Procurement/Legal, Other
• Who else will be actively involved in decisions for this engagement? (select all that apply) Options: Transmission Planning Manager, NERC Compliance Officer, VP Engineering/Executive Sponsor, Project Manager, Lead Modeler, Protection Engineer, Procurement, Legal/Contracts, IT/Security, Other
• Which RTO/ISO territory does the backlog and most studies fall under? Options: ERCOT, PJM, MISO, SPP, CAISO, NYISO, ISO-NE, Other
• How would you describe the emotional tone in the team about the backlog right now? Options: Calm/managed, Concerned, Stressed but coping, Urgent/panicked, Defensive/overworked, Other
• In one sentence, how would you describe the single most important problem you expect an external partner to solve?

Are We Running Out of Time?

• If the studies don’t clear on schedule, what is the most likely near-term consequence we face in the next 90 days? Options: Minor schedule slip with no penalties, Isolated RTO penalty risk, Missed audit deliverable, Customers withdrawing from the queue, Significant financial/RTO penalties, Other
• What is your current median study turnaround versus the RTO-required timeline? Options: Less than RTO requirement, Roughly meeting RTO requirement, 1.5x RTO requirement, 2x RTO requirement, More than 2x / unknown
• How large is the current backlog (number of studies)? Options: Less than 10, 10–50, 51–100, 101–300, More than 300, Unknown
• Approximately what percentage of the backlog is at immediate risk of being withdrawn by customers if timelines continue slipping? Options: Less than 5%, 5–20%, 21–50%, More than 50%, Unknown
• Describe any hard deadlines from RTOs or regulatory audits we must meet in the next 6–12 months (dates, deliverable type, consequences).

What's Really Breaking the Process?

• What recurring failure or friction most often causes studies to be sent back by the RTO or rejected internally?
• Which study types drive the majority of rework or delay for your team? (select all that apply) Options: Power-flow (steady-state), Short-circuit/SC, Transient/stability (transient/reactive), Protection coordination, Voltage/reactive planning, Generation interconnection impact studies, Load forecasting/renewables integration, Other
• Which modeling tools and formats create the most friction for you? Options: PSS/E, PowerWorld, PSLF, DIgSILENT PowerFactory, PSCAD, ETAP, Excel/custom scripts, Other
• How often do model validation or data-quality issues cause study rework? Options: Almost always, Often, Sometimes, Rarely, Never, Unknown
• Tell us about the last study that required major rework: what failed, how it impacted timelines, and how your team reacted.

Who Holds the Keys—and Who Can Stop the Train?

• If we delivered technically perfect results tomorrow, who could still block approvals—and what is their likely reason?
• Who is the formal decision maker for accepting external study work and associated budget? Options: Transmission Planning Manager, VP Engineering/Executive Sponsor, Procurement, NERC Compliance Officer, CFO, Board/Steering Committee, Other
• What formal escalation path exists when internal resources can’t meet RTO deadlines? Options: Executive escalation with budget approval, Emergency outsourcing authority, No formal path (ad-hoc), Operational workaround only, Other
• Which stakeholders require audit-ready documentation versus a technical memo or draft? Options: NERC Compliance Officer, RTO Liaison, Internal QA/Technical Review, Legal, External Auditor, Other
• How do you prefer external engineers to participate in RTO stakeholder meetings: your leads present, our engineers present, or a joint representation? Options: Your leads present, Our engineers present, Joint representation, Depends on meeting type, Other

If the Backlog Vanished Overnight…

• If the backlog were cleared tomorrow, what would change about how your department is judged in six months?
• Which metrics would prove backlog relief was successful for you? (select all that apply) Options: Number of studies closed, Average turnaround time, Percentage delivered on-time to RTO, Reduction in audit findings, Reduction in customer churn, Cost per study, Other
• What average turnaround per study would you consider acceptable for ongoing work? Options: Less than 1 week, 1–2 weeks, 2–4 weeks, 1–2 months, Depends on study type
• How much throughput (studies per month) would convince you the backlog is sustainably managed? Options: Less than 5, 5–15, 16–50, 51–100, More than 100
• If we had to prioritize, which study types should we clear first to reduce risk fastest? (select up to 3) Options: Generation interconnection impact studies, RTO-required power-flow studies, Stability/transient studies, Protection coordination, Short-circuit, Compliance deliverables for audits, Other

What Would an Auditor Celebrate?

• When auditors arrive, where are you most afraid they’ll find a gap?
• Which NERC reliability standards are highest priority for your next audit? Options: TPL (Transmission Planning), PRC (Protection & Controls), FAC (Facility Ratings), MOD (Modeling), CIP (Cyber Security), EOP (Emergency Operations), Other
• Which pieces of documentation do you currently lack or consider weakest for audits? (select all that apply) Options: Model validation reports, Study assumptions and bases, Version control logs, Reviewer sign-offs and traceability, Audit trail of data changes, Detailed RTO submittal packets, Other
• How mature and repeatable are your current model validation processes? Options: Mature and repeatable, Somewhat mature, Ad-hoc and inconsistent, Non-existent, Unknown
• Describe a past audit finding and how it affected operations, timelines, or credibility.

What Stands Between Talk and Deployment?

• What single constraint would prevent us from starting execution immediately if commercial terms were agreed today?
• Do we currently have access to the models, datasets, and simulation environments needed for the work? Options: Full access ready today, Partial access with conditions, No access but can be obtained, Access blocked by IT/security, Unknown
• Which security or onboarding requirements typically delay external engineers from accessing your models? (select all that apply) Options: NDA/contract, VPN/secure remote access, Data sanitization/anonymization, Vendor IT onboarding, Background checks, Other
• Are there known model limitations (missing topology, inaccurate dynamic data, or unsupported formats) we should flag now? Options: Yes — we will list them, Some known issues, None known, Unknown
• What mitigations would make you comfortable if models are imperfect at handover? (select all that apply) Options: Dedicated validation phase before studies, Conservative assumptions documented, On-site or remote joint model workshops, Field data sampling or telemetry checks, Staged deliveries with checkpoints, Other

Show Us the Proof — What Builds Trust Fast?

• What specific evidence would make you hand over priority studies to an external team on day one?
• Which reference attributes matter most when you check our past clients? (select all that apply) Options: On-time delivery against RTO timelines, Experience with similar system voltage classes, RTO acceptance history without rework, Senior engineer continuity, Quality of audit-ready reports, Cost predictability, Other
• Would you accept references from utilities of different size but similar technical complexity? Options: Yes, Maybe with caveats, No
• How important is single-engineer continuity (same senior engineer assigned throughout) to you? Options: Critical, Important, Nice-to-have, Not important
• Which demo deliverable would convince you fastest: a cleaned customer case, model validation summary, or a full RTO submittal packet? Options: Cleaned customer case, Model validation summary, RTO submittal packet, All three, Other
• Are there specific firms, projects, or types of references you want us to include—or avoid—when we prepare proof points?

What Would It Take to Say Yes?

• What unresolved objection would make you decline an otherwise technically solid proposal?
• Which commercial or SLA terms do you view as non-negotiable? (select all that apply) Options: Maximum study turnaround SLA, Penalty or remedy clauses for missed SLAs, Staffing duration commitment for senior engineers, Fixed-price per study option, Time-and-materials with capped budget, Confidentiality/data handling terms, Other
• What minimum duration of dedicated staffing would you require as a commitment from our senior engineers? Options: 1 month, 2–3 months, 3–6 months, 6–12 months, Project-dependent
• What governance cadence do you prefer for progress reviews and issue escalation during the engagement? Options: Weekly, Bi-weekly, Monthly, Daily during peak periods, As-needed
• What low-risk pilot would make you comfortable moving from evaluation to a signed commitment? Options: Single high-priority study pilot, Block of similar small studies, Model validation-only pilot, Short T&M sprint with defined scope, Other
• What final question should we ask you that we haven’t covered yet?

Start Here: What’s the One Thing We Should Fix First?

• In one sentence, what is the single most urgent study-related problem you want solved right now?
• Roughly how long is your current interconnection or planning study backlog? Options: Less than 1 month, 1–3 months, 3–6 months, 6–12 months, More than 12 months, Unsure
• How many discrete studies (interconnection or planning analyses) are in that backlog right now? Options: 1–5, 6–20, 21–50, 51–100, More than 100, Unsure
• Which RTO or regional process deadlines are driving this urgency? Options: PJM, MISO, SPP, ISO-NE, NYISO, CAISO, ERCOT, Other, Multiple/Not sure
• Who on your team is the day-to-day owner for clearing this backlog (title/role)?

Are You Closer to a Penalty Than You Think?

• If a regulator or RTO rejected a submission tomorrow, how quickly would that create financial or customer risk for you? Options: Immediate (days/weeks), Short (1–3 months), Medium (3–6 months), Longer (6+ months), Unsure
• Have you had missed deadlines or RTO pushbacks in the last 12 months? Tell us what happened and why.
• How often do interconnection customers threaten to withdraw from the queue because of study delays? Options: Frequently, Occasionally, Rarely, Never, Unsure
• What escalation path or executive intervention currently exists when a study deadline is at risk? Options: Formal executive escalation, Informal escalation, No clear escalation path, Unsure
• When a study is delayed, how does it typically impact stakeholder relationships (RTO, developers, regulators)?

What’s Really Causing the Queue to Grow?

• What internal assumption about your process would surprise you if it turned out to be false?
• Which study types dominate your backlog right now? Options: AC power flow (steady-state), Short-circuit/PSSE fault studies, Transient stability, Small-signal stability, Protection coordination, Renewable integration/electrical interconnection, HVDC/FACTS analysis, Other
• How well validated are the system models you'll need for RTO-quality studies? Options: Validated within last 3 months, Validated within 6–12 months, Stale (>1 year), Significant gaps / incomplete, No validated model available, Unsure
• What model elements are most likely to require rework (e.g., generator dynamic models, protection data, topology, governor/turbine data)?
• How frequently do model/data issues force you to re-run or redo work mid-study? Options: Almost always, Often, Sometimes, Rarely, Never

Who’s Doing the Heavy Lifting—and Where Are the Holes?

• Are you confident your current team composition can meet RTO expectations if given more headcount—why or why not? Options: Yes, with more headcount, No, skills or seniority gaps remain, Partially, for some study types only, Unsure
• Which engineering roles are you currently short on? Options: Senior transmission planners, Senior stability engineers, Modelers (PSSE/PowerFactory/etc.), Protection engineers, Documentation/compliance specialists, Project managers, Other
• How many senior engineers (with RTO study experience) are available to commit full-time to clearing the backlog? Options: 0, 1–2, 3–5, 6–10, More than 10, Unsure
• When junior staff are overloaded, what tasks are most often deferred or deprioritized?
• Have you used contractors or consultants previously to clear studies? What worked and what didn’t?

What Would Passing Your Next Audit Truly Mean?

• If an auditor inspected your study packets today, where would you expect to get called out?
• Which compliance frameworks or audit types are on your near-term horizon? Options: NERC TPL, NERC PRC, NERC FAC, State PUC audit, RTO compliance reviews, Internal compliance audit, Other
• How complete are the artifacts auditors typically request (analysis rationale, model validation logs, signed assumptions, traceable inputs)? Options: Complete and organized, Mostly complete with gaps, Fragmented across people/tools, Largely missing, Unsure
• Have prior audits resulted in findings tied to study documentation or modeling? If so, how severe were they? Options: Yes—major, Yes—minor, No findings, Not applicable / unsure
• How much time do you need to assemble compliance-ready reports for an audit starting today? Options: Less than 2 weeks, 2–6 weeks, 6–12 weeks, More than 12 weeks, Unknown

If We Could Wave a Wand, What Does Success Actually Feel Like?

• What throughput (studies per month) would relieve your queue to acceptable levels? Options: 1–5, 6–15, 16–30, 31–50, 50+
• What is the maximum acceptable turnaround time per study type (provide ranges if needed)?
• Which stakeholder groups must be satisfied for you to call the engagement a success (select all that apply)? Options: Transmission planning managers, NERC compliance officers, VP-level engineering, RTO contacts, Interconnection customers/developers, Procurement/finance, Other
• What specific acceptance criteria should we use to validate that backlog relief is effective (e.g., audit-ready reports, RTO acceptance on first submission, zero missed deadlines)?
• Beyond clearing the backlog, what organizational capability do you most want to leave as part of the handoff? Options: Model governance, Templates for audit-ready reports, Internal training for staff, Ongoing contractor support, Governance cadence

What Could Make a Good Plan Fail?

• What common project assumptions have bitten you before (e.g., model quality, data availability, stakeholder approval)?
• Who inside your organization can block a solution even if engineers agree it works, and why?
• What budget, procurement, or contracting constraints usually slow down engagements like this?
• How important is having on-site versus remote engineers for your stakeholder acceptance process? Options: Critical - must be on-site, Prefer on-site for key milestones, Remote is fine, Hybrid, Unsure
• If we delivered technically correct results but you couldn’t get internal sign-off, what would likely be missing?

Quick Snapshot: The Data We Need to Move Fast

• Pick the single biggest constraint we should prioritize first to move faster today. Options: Model validation, Senior engineer availability, Tool licensing and workflows, Data completeness, Procurement/contracting, Stakeholder alignment, Other
• Select the simulation tools your team uses regularly (choose all that apply). Options: PSS/E, PSLF, DIgSILENT PowerFactory, PowerWorld, PSCAD/EMT, CYME, Other
• How would you rate your model maturity on a practical scale for RTO studies? Options: Tier 1: Ready for immediate RTO submission, Tier 2: Needs limited validation, Tier 3: Significant rework required, Tier 4: Incomplete or missing models, Unsure
• Which staffing gaps are highest priority to fill right now? Options: Senior planners, Stability experts, Modelers, Protection engineers, Documentation specialists, Project management
• When is your next major audit, RTO submittal, or critical milestone? Options: Within 30 days, 30–90 days, 3–6 months, 6–12 months, No firm date / unscheduled
• Are there legal, confidentiality, or vendor restrictions we should know about before accessing models or data? Options: Yes - significant restrictions, Some restrictions but manageable, No major restrictions, Unsure

Ready to Take the Next Step (and What That Will Look Like)?

• If we proposed a rapid pilot to clear a tranche of studies, how quickly could you provide model access and primary contacts? Options: Within 1 week, 1–2 weeks, 2–4 weeks, More than 4 weeks, Unsure
• What level of engagement would satisfy your leadership today: advisory design only, co-execution with your team, or end-to-end delivery? Options: Advisory only, Co-execution, End-to-end delivery, Unsure / need discussion
• Which proof points would shorten your internal approval timeline (select all that apply)? Options: Reference utilities of similar size, Demonstrated RTO acceptance history, Signed SLAs for turnaround, Dedicated senior engineer assignments, Sample compliance-ready report
• What would a realistic governance cadence look like for you during an engagement (status, technical checkpoints, executive reviews)? Options: Weekly technical, Biweekly status, Monthly executive, Ad-hoc as needed, Other
• What concerns would you want us to proactively address in a statement of work to make signing easier?

Getting Oriented: Who’s In The Room and How Do We Reach Them?

• To get started, who from your team will be directly involved with a backlog-relief engagement (names, roles, and primary responsibilities)?
• Which stakeholders need to be kept informed versus those who must approve study deliverables? Options: Technical reviewers only, Technical + Compliance, Technical + Compliance + Executive approvals, All stakeholders for major milestones, Other
• Who holds the single point of contact (SPOC) authority for granting system/model access and signing off on final deliverables? Options: Transmission Planning Manager, NERC Compliance Officer, VP Engineering, IT/Security admin, Other
• What are the preferred real-time communication channels and document repositories your team uses today (pick all that apply)? Options: Email, MS Teams, Slack, SharePoint/Box, RTO portal, VPN/SFTP, Other
• What is your typical internal meeting cadence for technical workstreams and executive updates? Options: Daily standups, 2–3x weekly, Weekly, Biweekly, Monthly, Ad hoc

If This Keeps Going, What Breaks First?

• What is the single most severe consequence if your current backlog isn't cleared within the next RTO window (e.g., lost interconnection customers, RTO penalties, failed audit)? Options: Lost customers, RTO penalties, Failed NERC audit, Operational reliability risk, Regulatory scrutiny, Other
• How close have you come in the past year to missing an RTO submission or audit milestone because of capacity constraints? Options: We’ve missed before, We were within weeks, We met deadlines but strained resources, Never close
• When backlog-driven delays occur, how does that typically feel for your team and executive leadership? Tell us about a recent moment that still sticks with you.
• Which external consequences worry you most: stakeholder defections, financial penalties, reputational damage, or regulatory findings? (Rank top two.) Options: Defections, Financial penalties, Reputation, Regulatory findings, Operational reliability
• Has your organization previously tried outsourcing study work? If so, what went wrong or right with that experience?

How Honest Is Your Model? (And How Far From Reality Are We Willing to Go?)

• What known limitations in your network models cause you the most concern—missing topology, inaccurate equipment parameters, generation dispatch assumptions, or dynamic model gaps? Options: Topology errors, Equipment parameter gaps, Outdated generator models, Inverter/dynamics not modeled, Load modeling inaccuracies, Other
• When was the last full model validation performed, and what were the biggest issues uncovered? Options: Within 3 months, 3–6 months, 6–12 months, Over a year, Unknown
• Have you quantified how model inaccuracies changed past study results or caused rework with the RTO? Give a concrete example.
• Which dynamic model types (e.g., WECC models, IEEE-type exciters, inverter-based resources) routinely fail validation or require extra effort to model correctly? Options: Synchronous machines, Inverter-based resources, Protection models, HVDC, FACTS devices, Other
• What level of residual uncertainty is acceptable for you in a delivered study (e.g., conservative assumptions, sensitivity runs, or independent validation)? Options: Conservative assumptions ok, Require sensitivity studies, Want independent validation, Must match internal baseline

Can We Actually Get the Data and Environments We Need?

• Which simulation platforms and file formats host your planning models today (select all that apply)? Options: PSS/E (.raw/.sav/.dyr), PSLF, PowerWorld, GE PSLF, Matlab/Simulink, Custom/Other
• How quickly can your IT/security team provision access credentials, VPN, or SFTP to external consultants once requested? Options: <3 business days, 3–7 business days, 1–2 weeks, 2+ weeks, Depends on approvals
• Are there legal, regulatory, or vendor restrictions that limit sharing of models or raw telemetry with third parties? Options: Yes—strict restrictions, Some restrictions with NDA, No restrictions, Unsure
• Who owns the canonical model repository and who is allowed to make changes during an engagement? Options: Internal planning team only, Internal + consultant with controls, Consultant can update with approval, Other
• If we asked for a small sample model and a representative study case to validate our process, how quickly could you provide it and in what format?

Who Owns What When We Work Together?

• If we take on studies, which responsibilities will you retain (e.g., model provisioning, final sign-off, RTO liaison, data approvals)? Options: Model provisioning, Final sign-off, RTO liaison, Internal QA, Other
• Describe your internal approvals workflow for study deliverables—how many review layers, typical reviewers, and approval SLAs.
• What acceptance criteria do you require for a study to be considered 'compliance-ready' for an audit or RTO submission? Options: Full report + raw files, Executive summary + validation logs, Detailed calculations + traceability, Other
• Are there internal templates, checklists, or naming/version conventions consultants must follow to avoid rework? Options: Yes—detailed templates, High-level templates only, No templates, Unsure
• How do you prefer change control to work when we propose modeling adjustments: immediate updates, staged approvals, or offline sandbox testing first? Options: Immediate updates with approval, Staged approvals, Sandbox & test then approve, Other

What Would Make You Sleep Better at Night?

• What are your top three risk tolerances for an external team running studies on your models (e.g., accuracy, confidentiality, timeline, regulatory opinion)? Options: Accuracy, Confidentiality, Timeline, Regulatory alignment, Cost
• Would you require an independent validation step or third-party audit of our results before submission to the RTO? If so, under what conditions? Options: Always required, Only for critical studies, No, not required, Unsure
• What mitigation strategies would you find acceptable if models show systemic errors—rollback to baseline, sensitivity envelopes, expedited on-site validation, or other? Options: Rollback, Sensitivity envelopes, Expedited validation, Hybrid approach, Other
• How important is traceability (line-by-line calculation logs, model change history) for audit defense? Choose the minimum acceptable level. Options: Full traceability required, Key changes + summaries, Executive-level traceability only, Minimal
• If a recommended model correction implies capital work or design changes, how does your organization prefer to surface and escalate that as a risk? Options: Technical review -> Exec, Log in shared backlog, Raise to compliance immediately, Other

How Should We Work Day-to-Day Without Getting in Each Other’s Way?

• What interim deliverables and cadence would make you feel comfortable that progress is visible and manageable? Options: Weekly status + interim results, Biweekly deep dives, Milestone-based only, On-demand reports
• Which collaboration tools must we use to exchange files and track issues (pick all that apply)? Options: SharePoint/Box, Jira/ServiceNow, Email, MS Teams/Slack, RTO document portal, Other
• When technical disagreements arise with your team or the RTO, what escalation path do you want us to follow? Options: Technical working group, Project steering committee, Direct to SPOC, RTO escalation per procedures, Other
• How do you want interim model updates communicated—annotated model change logs, highlighted diffs, or side-by-side case comparisons? Options: Change logs, Highlighted diffs, Side-by-side cases, Combined package
• What level of on-site presence (if any) do you expect from our senior engineers during critical RTO meetings or model handoffs? Options: On-site for key meetings, Remote attendance sufficient, Hybrid as needed, On-call only

Timing Is Everything — What Dates Can’t Move?

• What are the immovable external deadlines we must design around (next RTO study window dates, NERC audit windows, customer notice deadlines)? Please list dates.
• For the backlog you want cleared, what turnaround per study would be considered acceptable (pick closest)? Options: <1 week, 1–2 weeks, 2–4 weeks, 4–8 weeks, Depends on study type
• How much schedule flexibility do you have if additional validation or remediation is required after initial results? Options: None—must meet deadlines, Small buffer (1–2 weeks), Moderate (3–6 weeks), Flexible
• Do you have blackout periods (e.g., peak operational seasons) where we should not schedule heavy simulation runs or stakeholder meetings? Options: Yes—list periods, No
• If we proposed a phased approach with high-priority cases first, which subset of the backlog should be prioritized and why?

If We Delivered Perfectly, What Would Change for You?

• What specific metrics will you use to judge whether the engagement cleared the backlog (throughput target, percent of queue resolved, on-time submittals)? Options: Throughput per month, Percent queue resolved, On-time submittal rate, Reduction in rework, Audit readiness
• Describe the ideal handoff: what documentation, training, and institutional knowledge must we leave behind so your team can operate independently?
• How would you like lessons-learned or continuous improvement items tracked after the engagement—single backlog, recurring review, or integrated into your PMO? Options: Shared backlog, Recurring review meetings, Integrated PMO, Other
• Beyond immediate backlog relief, what longer-term capabilities would you most like to gain from this engagement (e.g., faster in-house modeling, better QA processes, trained staff)? Options: Faster in-house modeling, Improved QA, Trained staff, Stronger RTO relationships, Other
• What would constitute a red flag at closeout that would make you classify the project as only partially successful? Options: Unresolved model issues, Missing audit documents, High rework rate, Lack of knowledge transfer, Other

Ready to Commit? The Practical Checklist We’ll Need Before We Start

• Which of the following must be in place before we begin model work (select all that apply)? Options: Signed SOW/contract, NDA in place, System access credentials, Sample model & case, SPOC assigned, Security review complete
• Who will approve the initial statement of work and who signs off on start-of-engagement readiness? Options: Transmission Planning Manager, NERC Compliance Officer, VP Engineering, Procurement, Other
• What are the top three items still blocking a 'go/no-go' decision today?
• How would you like to validate our process before full-scale work—small pilot study, dry-run on a sanitized model, or reference check with a similar utility? Options: Pilot study, Sanitized dry-run, Reference check, Other
• Assuming approvals go smoothly, what is your target start date for pre-deployment activities (access provisioning, sandbox tests, kickoff)? Options: Within 1 week, 1–2 weeks, 2–4 weeks, 1+ month, Unsure

Opening: Where We Stand Together

• In one sentence, what is the single deliverable you must have validated and handed off for your next RTO milestone or audit?
• What is the firm deadline (RTO submission window or audit date) we must meet for that deliverable? Options: Within 2 weeks, 2–4 weeks, 1–2 months, 2–3 months, 3+ months
• Who are the 2–4 internal decision-makers who must be satisfied before the handoff is accepted (titles and roles)?
• How frequently do you currently get status updates about studies that are planned for handoff? Options: Daily, 2–3x/week, Weekly, Biweekly, Monthly, Only on request
• Tell us about a past handoff that felt smooth—what specifically made it work?

If Our Reports Don’t Pass, What Collapses?

• What is the worst practical consequence for you if the validated results are rejected by the RTO or fail an audit? Options: Financial penalties, Project delays / customer defections, Repeat studies & extra cost, Regulatory enforcement, Reputational damage, Other
• Have you experienced a rejected submission or audit finding before? If yes, what unfolded and how long did remediation take? Options: Yes—minor finding (days-weeks), Yes—major finding (months), No, never, Not sure
• How confident are you in your current models and assumptions to withstand auditor scrutiny? Options: Very confident, Somewhat confident, Unsure, Not confident
• Which stakeholder reactions worry you most if we discover issues during validation (e.g., exec escalation, interconnection customers, NERC)? Options: Executive escalation, Loss of interconnection customers, RTO pushback, NERC audit finding, Internal resource reallocation, Other
• When something has gone wrong in the past, who in your organization had to own the remediation—and how did that feel for them?

Where Acceptance Criteria Still Feel Fuzzy

• Tell us where your acceptance criteria are unclear or are debated between stakeholders?
• Who originally defined the acceptance criteria for studies (internal team, RTO templates, consultants, legal/compliance)? Options: Internal planning team, RTO procedural templates, Previous consultant, Compliance/legal, Combination
• Which of the following must be explicitly demonstrated in your acceptance test to sign off on a study? Options: Model parity with utility master, Reproducible run scripts, Result reconciliation to baseline, Documented assumptions, QA check logs, Executive summary with mitigation path
• What numeric tolerances or pass/fail thresholds do you require (e.g., powerflow mismatch limits, stability margin thresholds)? Please list values or indicate 'not defined'. Options: Not defined, Defined and documented, Partially defined
• If an acceptance criterion is not met, what is your preferred remediation path—re-run with adjusted inputs, alternative mitigation, or escalate for capital work? Options: Re-run with corrections, Alternative mitigation (operational), Design capital project, Escalate to executive decision, Undecided

Can Your Team Own This After We Leave?

• How would you describe your internal team's capability to maintain validated models and run the same validation suite independently? Options: Fully capable, Mostly capable with light coaching, Needs significant upskilling, Not capable
• Which internal roles will be responsible for day-to-day model maintenance and for compliance evidence after handoff?
• What handoff formats make your team most comfortable—detailed runbooks, recorded walkthroughs, live shadow sessions, or transfer of simulation licenses? Options: Detailed runbooks, Recorded walkthroughs, Live shadowing sessions, Transfer of licenses & scripts, On-site training, Other
• How long does your team usually need to reach independent competence on a new model or process, measured in weeks? Options: <1 week, 1–2 weeks, 3–4 weeks, 1–3 months, 3+ months
• Describe a knowledge transfer that failed in the past—what was missing and how would you avoid that this time?
• After handoff, would you prefer a bundled post-engagement support window (weeks of on-call support) or on-demand consulting hours? Options: Bundled on-call window, On-demand hours, No post-engagement support needed, Unsure

Audit-Ready Reporting: What Would Convince an Auditor?

• If an external auditor examined the package we deliver, what 3 pieces of evidence would make them stop asking questions?
• Which report elements are non-negotiable for your compliance team (e.g., change logs, model lineage, input datasets, QA checklists)? Options: Model lineage and versions, Input dataset snapshots, QA checklists and signoffs, All run scripts and seed files, Executive summary tied to requirements, Mitigation tracking
• Do you require any specific formatting, templates, or document control systems for audit artifacts (e.g., SharePoint, PDF with signature stamps)? Options: SharePoint versioned, PDF with signatures, ISO-style document control, RTO-specific template, No preference
• Who in your organization will be responsible for presenting these reports during the audit, and what level of technical detail do they prefer? Options: Technical lead (detailed), Compliance officer (high-level), Executive (summary), RTO liaison (procedural), Multiple roles
• Have auditors previously asked for traceability from raw input to final recommendation? If so, what gaps did they highlight? Options: Yes—traceability required, Yes—some traceability expected, No, not required before, Not sure

Risk, Assumptions, and Tradeoffs You're Willing to Live With

• Which modeling or data limitations are you already accepting for this engagement (e.g., simplified protection, steady-state approximations, aggregated resources)? Options: Steady-state approximations, Aggregated DER representation, Simplified protection models, Historic load shapes vs. real-time, None—must be full fidelity
• What residual risk level is acceptable to leadership if we document it clearly—low (minor), medium (manageable), high (requires exec sign-off)? Options: Low, Medium, High—exec sign-off required
• If a recommended mitigation requires capital investment beyond current budgets, how do you prefer we present the tradeoff (Tiered options, cost-benefit, or deferred actions)? Options: Tiered options, Cost-benefit analysis, Deferred/temporary operational fixes, Recommend escalation
• Who must formally accept the stated assumptions and residual risks before we close the handoff? Options: Planning Manager, Compliance Officer, VP Engineering, Legal/Regulatory, Cross-functional governance
• Tell us about an assumption that surprised stakeholders later—how would you like to prevent that on this engagement?

Timing, Sign-Offs, and the Last-Mile Process

• Who holds the final sign-off authority to declare a study 'validated and handed off' in your organization? Options: Planning Manager, Compliance Officer, VP Engineering, RTO Liaison, Governance Board
• What is your ideal sign-off timeline once we submit the compliance-ready report? Options: Same day, 1–3 business days, 4–10 business days, 2–4 weeks, Longer—depends on governance
• Which artifacts must be delivered before a sign-off vote—full dataset package, executive summary, QA checklist, recorded handoff session, or other? Options: Full dataset package, Executive summary, QA checklist, Recorded handoff, Acceptance test results, Other
• Do you have a formal governance cadence (weekly steering, biweekly review) for closing handoff items and tracking action lists? Options: Weekly steering, Biweekly review, Monthly review, Ad-hoc as needed, No formal cadence
• Are payment milestones or contract closure tied to the sign-off? If yes, how should we align deliverables and invoicing? Options: Yes—payment on sign-off, Partial payment on delivery + sign-off, No tie to payment, Undecided

How This Should Feel—Short-term Wins and Long-term Confidence

• Imagine it's three months after handoff and everything is working—what are the three visible signs that made you feel the engagement succeeded?
• Which post-handoff metrics would you like us to help you monitor (e.g., study turnaround time, audit finding count, model drift indicators)? Options: Study turnaround time, Audit findings count, Model drift indicators, QA pass rate, Stakeholder satisfaction
• Would you value a short 'lessons learned' session and a prioritized backlog at close, or prefer only a formal report? Options: Lessons learned + backlog, Formal report only, Both, Neither
• How would a small early win (e.g., a quick validated study delivered within days) change stakeholder sentiment internally? Options: Calm executives, Retain interconnection customers, Reduce audit anxiety, Improve team morale, All of the above
• Finally, what single reassurance or guarantee would make you most comfortable moving this validation and handoff forward with us?