A quick program snapshot

• Which of these best describes your program's primary funding source? Options: Voter-approved bond measure, Board-authorized capital allocation, Hospital capital plan, Corporate capex budget, Mixed funding sources, Other
• Approximately how many active projects will this program oversee at peak delivery? Options: 1-5, 6-10, 11-20, 21-50, More than 50
• Give a one-sentence summary of the program outcomes your board or governing authority expects.
• Who in your organization is ultimately accountable to the board or funding authority for program delivery and budget performance? Options: Chief Capital Officer, VP Facilities, Program Director, Finance Director, Other
• Which target window best matches your expected program duration from mobilization to final acceptance? Options: Under 12 months, 12 to 24 months, 24 to 48 months, Over 48 months

Where the program feels fragile

• If a single budget overrun forced you to cut or pause one project, which project would you drop and why?
• Which governance or reporting gap has most often allowed cost or schedule surprises to grow before leadership sees them? Options: Infrequent executive reporting, No program-level forecasting, Siloed project teams, No common risk register, Other
• Tell me about the last time a schedule dependency between projects caused rework or cost increases, and how you recovered.
• Which single funding or approval gap could stop the program in its tracks if it is not fixed within your next quarter?
• How often do you update program-level cost forecasts and share them with executive stakeholders? Options: Weekly, Biweekly, Monthly, Quarterly, On major milestones only

How decisions actually get made

• Who in your governance chain can pause funds or change scope without returning to the full board? Options: Program Director, Chief Capital Officer, Finance Director, Board committee, No one
• Walk me through the typical approval timeline from a program-level decision to contractor notice to proceed, in business days.
• Which forum receives your consolidated program dashboard today, and how often? Options: Executive team weekly, Board monthly, Capital committee monthly, Ad hoc on request, No consolidated forum
• Is there a named decision-maker who has authority to sign final program acceptance within your target closeout window? Options: Yes, named and authorized, Yes, but needs board ratification, No, decision delegated to committee, Not yet assigned
• How would you describe leadership's tolerance for tradeoffs between schedule, scope, and cost? Options: Schedule-first, Cost-first, Scope-first, Balanced depending on milestone

Master schedule and shared pressures

• Which shared resource or milestone, if delayed four weeks, would cascade delays across more than three projects?
• Which tool does your team use today to manage the program master schedule and cross-project dependencies? Options: Primarily spreadsheets, Single scheduling tool (P6/MS Project), Multiple tools with manual consolidation, Owner's internal dashboard, Other
• When dependencies slip, who is usually responsible for sequencing recovery actions and communicating them to stakeholders? Options: Program manager, Project managers, Owner's PMO, Contractor lead, No single accountable party
• Do you have a hard occupancy, regulatory, or funding-driven date that cannot move without significant consequence? Options: Yes, fixed date with penalty risk, Yes, but negotiable, No fixed date
• Describe your current contingency planning approach for shared-site conflicts or utility shutdowns.

Where stakeholders feel the strain

• Which stakeholder group has publicly pushed back on program pace, budget, or disruption in the last 12 months? Options: Board or governing authority, Community or neighborhood group, Facility operations, Finance office, Other
• How does pushback typically surface, and who receives the first alert? Options: Formal board inquiry, Operational leadership email, Public comment or media, Internal escalation to program director, Other
• Tell me about a recent stakeholder conflict that required a change to scope, schedule, or budget, and what tradeoff was chosen.
• Which of these outcomes would make your stakeholders call for an independent review of program controls? Options: Recurring budget variances, Missed critical milestones, Safety incidents, Poor public communication, Other
• Who needs to be convinced internally for a change in program delivery approach to proceed quickly? Options: Chief Capital Officer, Finance Director, Operations or Facilities exec, Board chair, Procurement lead, Other

Top program risks that would pause delivery

• Which single site condition, permit, or funding shortfall would pause work immediately if unresolved?
• Which of the following are active or likely constraints on your timeline today? Options: Pending permits, Utility relocation agreements, Unknown site conditions, Incomplete design packages, Funding not yet fully authorized, Other
• Who owns mitigation for your top program risks today, and do they have named deputies? Options: Program director with deputies, Project managers own risks, Risk owner not assigned, Shared ownership across teams
• Are there any active legal holds, permit suspensions, or public litigation that would prevent mobilization? Options: Yes, No, Unsure
• How quickly could your team produce an agreed program-level risk register and mitigation plan if requested? Options: Within 1 week, Within 2-3 weeks, Within a month, Longer than a month, Not currently available

The other options you're weighing

• Which alternatives to an external program management partner are you actively evaluating? Options: Incumbent PM firm, Expanding internal PMO, Owner's rep model, Design-build single-vendor, Temporary staffing agency, Other
• Who is currently the incumbent or most familiar external partner on your program, if any? Options: Incumbent external PM firm, No external partner, Contractors handle PM work, Other
• What would have to be true about your current internal approach for you to decide to keep it rather than engage an outside partner? Options: Full funding and staffed PMO, Proven forecast accuracy, Documented program standards, Named delivery leads, Other
• Has anyone proposed solving this with internal hires or temporary staff instead of a program-level firm? Options: Yes, internal hires proposed, Yes, temporary staffing proposed, No one has proposed DIY, Unsure
• If your incumbent offered an accelerated governance package without additional cost, what would stop you from staying with them?

Readiness facts that must be true

• Which of the following readiness items is NOT in place today and would block mobilization? Options: Executed funding resolution, Site access agreements, Named site owners or custodians, Baseline design packages, Data and reporting access, IT credentials for contractor systems, Required permits
• Which systems must integrate with program reporting or dashboards for delivery to proceed, and who controls those integrations? Options: ERP/Financial system, Project scheduling system, Document management, Asset management, No integrations required, Other
• How many dedicated owner-side staff are available to support a vendor-led mobilization, for example program admin, procurement, or site liaisons? Options: 0, 1-2, 3-5, 6-10, More than 10
• Is your program data (cost history, schedule baselines, permits) centralized and accessible for a new delivery partner to review within two weeks? Options: Yes, centralized and ready, Partially available, No, not centralized, Unsure
• Do you have an executed funding resolution that would support vendor mobilization within your desired mobilization window? Options: Yes, No, Funding committed but not executed, Unsure

How you'll know we succeeded

• Which measurable success metric, if not improved, would make you view the engagement as unsuccessful? Options: Program-level cost variance, Master schedule adherence, Stakeholder satisfaction scores, Number of change orders, Closeout and warranty resolution time
• If the program meets 90% of milestones and stays within 5% of the authorized budget, would that satisfy your board for final acceptance and closeout? Options: Yes, likely, Yes, with minor exceptions, No, board requires stricter targets, Unsure
• Which reporting cadence and format does your executive team prefer for program-level updates? Options: Weekly one-page dashboard, Biweekly narrative and dashboard, Monthly board packet, Real-time dashboard access, Ad hoc deep dives
• Describe a deliverable, beyond numbers, that would make leadership feel confident the program is controlled.
• Who must sign off on final acceptance and release of the final billing milestone? Options: Board chair, Chief Capital Officer, Finance Director, Program Director, Other

What would make this an easy yes

• If a pilot reduced near-term cost uncertainty by a measurable amount, what internal decision would need to be taken for you to sign within 30 days?
• Which procurement path are you most likely to use to engage a program management partner? Options: Direct award to incumbent, Formal RFP/competitive process, Request for qualifications then interview, Sole source with board approval, Other
• Who will be on the evaluation committee and what minimum information do they expect to see before recommending award?
• Which documents or approvals must be in place before you can issue a mobilization notice? Options: Signed contract, Insurance and bonds, Funding execution, Site access agreements, Permits, Other
• Who must sign the mobilization notice to start vendor work, and how quickly can they provide that signature once conditions are met?

• Program Delivery Walkthrough

• Confirm the current state and its cost to your program
• You confirm that the demonstrated master schedule eliminates the site access and utility conflicts you described.
• Provide current project baselines, key site access constraints, and funding milestone dates for the conflict and forecast analysis.
• You confirm the program-level budgeting approach would surface cost escalation early enough to preserve funding milestones.
• Walk through master schedule coordination using your project example
• Run a master-schedule clash analysis on the provided baselines and deliver a conflict report prior to the follow-up session.
• Demonstrate program-level budgeting and forecast reconciliation
• Share the executive reporting requirements and any board or funding authority decision deadlines.
• You agree the proposed reporting package satisfies the governance and board-level decision requirements.
• Show risk controls and escalation workflows in the program context
• You identify the remaining evidence or deliverables required before a staffing and commercial mutual commit.
• Draft a one-page program budget reconciliation that maps current project forecasts to program contingency and deliver before the decision meeting.
• Review stakeholder reporting cadence and executive package
• Validate the future state
• Agree next evidentiary steps toward a mutual commitment

• Program Delivery Walkthrough
• Program Delivery Walkthrough Deck
• Program Delivery Solution Brief

• meeting
• slides
• document

• Operate On‑Site Program Management Office
• Maintain Program‑Level Budget and Forecasts
• Manage Master Program Schedule
• Oversee Project Construction Management and Milestones
• Implement Program‑Level Risk Management
• Coordinate Procurement Strategy and Contractor Prequalification
• Develop and Enforce Design and Construction Standards
• Provide Stakeholder Reporting and Executive Dashboards
• Administer Change Order and Contingency Controls
• Manage Inter‑Project Site Access and Utility Sequencing
• Deliver Program Closeout and Lessons Documentation
• Coordinate Funding Compliance and Board Reporting

Operate On‑Site Program Management Office

• Who will be the program director you expect to have on-site full time, and what explicit approval authority (for example, change orders up to $50,000) should they hold in your governance structure?
• Which physical location will host the on-site PMO for the program: dedicated room in an existing facility, temporary trailer on site, or shared administrative space? Options: Dedicated room on a campus/site, Temporary construction trailer, Shared administrative space, Hybrid (onsite + remote)
• How many full-time equivalent (FTE) PMO staff do you expect by role (program director, project managers, cost engineer, scheduler, admin) at peak mobilization? Options: Program director only (1), Small PMO (2-4 FTE), Core PMO (5-9 FTE), Large PMO (10+ FTE)
• List the site access hours, badge requirements, and any contractor/visitor check-in artifacts the PMO must enforce for construction zones and data rooms.
• Do you require the PMO to maintain an on-site project controls suite (cost ledger, schedule baseline files such as MS Project or Primavera, and a document repository)? Options: Yes, full on-site project controls suite, Partial (document repository only), No, remote controls acceptable
• Provide any site-specific safety procedures, lockout/tagout (LOTO) rules, or contractor safety plan standards the PMO must enforce.

Maintain Program‑Level Budget and Forecasts

• Which funding sources (for example: voter-approved bond, capital reserves, state grant) and their board-approved amounts must be tracked in the program budget? Options: Bond funds, Capital reserves, State grants, Federal grants, Other
• How often do you require program-level forecast updates and a board-ready variance report: monthly, quarterly, or other cadence? Options: Monthly, Bi-monthly, Quarterly, Other
• Identify the cost estimate classification or confidence level you want for baseline budgets (for example: Class 3 estimate, contingency percentage) and how contingency should be handled. Options: Class 3 (schematic-level), Class 2 (design-development), Class 1 (construction-ready), Specify custom rule
• What defines acceptance for program-level forecast accuracy (for example: rolling three-month forecast variance within 5% of actuals) that will be reported to the board? Options: Variance within 2%, Variance within 5%, Variance within 10%, Custom threshold
• List the accounting code segments or chart of accounts mapping the PMO must populate for payment applications and financial forecasts.
• Do you require ledger-level reconciliation evidence for monthly board reporting such as reconciled invoices, payment applications, and bank draw schedules? Options: Yes, monthly reconciliations required, Yes, quarterly reconciliations required, No, summary-level reporting only

Manage Master Program Schedule

• Who will be the named owner for master schedule updates and who has authority to approve baselining changes?
• Specify the scheduling tool your organization uses as standard for master program control (for example: MS Project, Primavera P6, or an internal schedule repository). Options: Microsoft Project, Primavera P6, Integrated construction management platform, Other / Unspecified
• Indicate the update cadence required for critical path and milestone variance analysis to be distributed with executive reporting. Options: Weekly, Bi-weekly, Monthly, Ad-hoc as milestones change
• Provide the inter-project dependencies that must be modeled in the master schedule, including shared site access windows, crane availability, and utility shutdowns.
• What acceptance criteria will validate the master program schedule baseline (for example: linked project schedules with no unresolved logic gaps, approved milestone list, float allocation rule)?
• When are your long-lead procurement milestones and permit milestone dates that must be locked into the master schedule?

Oversee Project Construction Management and Milestones

• Name the single point of contact for construction RFIs and submittal approvals for each project module and describe their expected review SLA.
• Identify which project milestones will require direct program oversight and escalation (for example: substantial completion, certificate of occupancy, final commissioning). Options: Substantial completion, Certificate of occupancy, Systems commissioning, Other key milestones
• Describe the preferred routing and documentation for change order approvals when contractor requests exceed specified thresholds.
• Specify the acceptance documents you require at each milestone such as signed punchlist, commissioning report, and temporary occupancy permit.
• Are on-site QA/QC inspection checklists, independent third-party testing reports, or both required during structural and MEP milestones? Options: On-site QA/QC checklists only, Third-party testing reports only, Both checklists and third-party reports, Neither
• Estimate the typical duration you expect between substantial completion and owner acceptance for a standard project in the program. Options: Less than 2 weeks, 2-6 weeks, 6-12 weeks, More than 12 weeks

Implement Program‑Level Risk Management

• Designate who will chair program-level risk review meetings and which owner governance roles (for example CFO, operations director) must be invited.
• Select the risk register format you prefer: spreadsheet with scoring, integrated schedule-cost-risk tool, or a formal risk management plan with mitigation owners. Options: Spreadsheet risk register, Integrated risk module (tool), Formal risk management plan, Other
• Indicate how program contingency should be allocated across projects: a single program contingency bucket, project-level contingencies, or a hybrid approach. Options: Single program contingency bucket, Project-level contingencies only, Hybrid (program + project contingencies)
• Compile the top 10 program risks from your perspective (examples: funding shortfall, utility delays, contractor insolvency) that should be prioritized in the initial register.
• Are there specific regulatory regimes we must track in the risk register such as prevailing wage compliance, DBE goals, or state grant audit requirements? Options: Prevailing wage, DBE/MBE goals, State grant audit rules, Federal funding compliance, None of the above
• When do you want quarterly risk heat maps and mitigation progress reports presented to executive sponsors and the board for funding covenants? Options: Quarterly aligned to board meetings, Quarterly at month-end, Monthly, Other cadence

Coordinate Procurement Strategy and Contractor Prequalification

• State the procurement routes expected across the program (for example: design-bid-build, design-build, construction manager at-risk). Options: Design-bid-build, Design-build, Construction manager at-risk, Mixed approach
• Define the contractor prequalification criteria to be included in the PQQ (for example: years of relevant experience, bonding capacity, safety EMR, litigation history).
• Name who on your team will approve shortlists and who will sign final contractor selections for program-level procurement.
• Confirm whether certified payroll verification and bonding verification are required during contractor onboarding and monthly compliance checks. Options: Certified payroll and bonding verification required, Bonding verification only, No verification required
• Outline any mandatory DBE/MBE participation targets, local hire requirements, or subcontracting goals that must be included in procurement documents.
• State the intended prequalification window opening and closing dates relative to the RFP release and bid due date.

Develop and Enforce Design and Construction Standards

• Reference the existing design standards or specification sets the program must adopt such as campus master design standards, CSI specification divisions, or agency boilerplate.
• Describe how deviations from standard details should be documented and routed for approval (for example: design exception form or engineering change notice).
• Confirm whether you require a standards compliance checklist tied to design submittals and construction milestones. Options: Yes, compliance checklist required, Optional, No
• Give the file format and naming convention required for record drawings and as-built submissions (for example: PDF with title block, layered CAD files) at project closeout. Options: PDF (single file), PDF + native CAD files, Revit/BIM deliverable, Other
• Designate who will own change control for specification modifications and who must sign off on variances from program standards.
• Select whether you require performance-based specifications for MEP systems (for example: HVAC commissioning thresholds, acoustic limits) or prescriptive standards. Options: Performance-based specifications, Prescriptive specifications, Mixed approach

Provide Stakeholder Reporting and Executive Dashboards

• Choose the KPIs that must appear on the executive dashboard for board reporting (for example: program budget remaining, schedule variance, percent complete by project). Options: Program budget remaining, Schedule variance, Percent complete by project, Risk heat map, Change order exposure
• Tell us the preferred frequency and format for board-ready reports (for example: monthly PDF packet, quarterly slide deck, live dashboard link). Options: Monthly PDF packet, Quarterly slide deck, Live dashboard link, Other
• Will you require role-based dashboards with separate views for executives, program managers, and site supervisors? Options: Yes, three-tier views required, Yes, two-tier views, No, single dashboard for all
• Enumerate the data sources we must integrate into dashboards such as ERP financial feeds, change order log, schedule baseline files, and commissioning reports.
• Clarify any specific board covenants or grant reporting formats we must adhere to when publishing executive reports.
• Estimate the maximum number of concurrent dashboard users and whether external stakeholders such as a bond oversight committee require view-only access. Options: 1-10 users, 11-50 users, 51-200 users, 200+ users

Administer Change Order and Contingency Controls

• Define the approval tiers and dollar thresholds for contingency draw requests and change orders.
• Detail the change-order documentation that must accompany each request (cost breakdown, time impact analysis, revised schedule logic).
• Mark which cost control ledgers must be updated when a change order is executed (for example: project budget, program contingency, owner allowance). Options: Project budget ledger, Program contingency ledger, Owner allowance ledger, All of the above
• Clarify any predefined contingency release rules you expect (for example: percentage releases at milestones, holdbacks until certificate of occupancy).
• Tell us whether you require independent cost verification prior to releasing funds for changes above a specified threshold and define that threshold if applicable. Options: Yes, independent verification required, No independent verification, Only for changes > specified threshold
• Would you like monthly roll-up reports of change orders showing a running contingency balance and forecast to completion? Options: Yes, monthly roll-up required, Quarterly roll-up acceptable, No roll-up required

Manage Inter‑Project Site Access and Utility Sequencing

• Pinpoint which campuses or sites within the program share access constraints that require a phased site access plan.
• Recommend scheduling rules for crane and hoisting windows across adjacent projects to prevent conflicts (for example: staggered weekly windows, shared equipment booking).
• Give the municipal contacts or departments we must coordinate for utility shutdown permits (water, power, telecom) and any standing permit numbers.
• Explain whether preapproved traffic control plans and lane closure permits exist for the sites or whether the PMO must prepare lane closure applications. Options: Preapproved plans exist, PMO must prepare applications, Mixed by site
• Quantify the typical percentage overlap you expect between adjacent project activities during peak construction (for example: 10-30%) to help size coordination staffing. Options: Less than 10%, 10-30%, 30-50%, More than 50%
• Document the site-specific permit artifacts that must be stored in the program document repository (for example: issued permits, traffic control plans, utility shutdown approvals) and indicate who issues them.

• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Fee Schedule & Payment Terms
• Staffing & Resource Commitment
• Mobilization Milestones & Dependencies
• Governance & Reporting Agreement
• Change Order & Scope Amendment Agreement
• Insurance & Certification of Coverage
• Regulatory Compliance Addendum (conditional)

• Go-live Health Check
• First Measurement Review
• 90-Day Outcomes and Lessons Review
• Quarterly Program Success Review
• Annual Closeout, Warranty and Enhancement Review

• Update the executive dashboard with agreed metric definitions and next-quarter targets.
• Deliver the lessons-learned summary and recommended process changes for program standards.
• Create the warranty and enhancement request triage board and define SLA tiers and response timelines.
• Executive metric trends
• Confirm whether quarterly trends require executive remediation or are within acceptable tolerances.
• Agree the top 3 program priorities and remediation actions for the upcoming quarter.
• Ensure warranty and enhancement items are triaged with timelines for resolution or deferral.
• Re-confirm agreed success criteria and owners
• Publish the quarterly remediation plan for any metrics outside tolerance with target close dates.
• Reconcile the warranty and enhancement backlog and mark items for resolution or deferral.
• Cumulative outcomes vs targets
• Archive a final outcomes report comparing cumulative metrics to Outcome Discovery targets for institutional record.
• Agree a documented warranty SLA and enhancement lifecycle with the shared channel owner identified.
• Finalize and distribute the lessons-learned archive and required updates to program delivery standards.
• Publish the annual closeout report that maps cumulative outcomes to Outcome Discovery targets.
• Document and activate the warranty SLA, triage workflow, and the shared tracking channel.
• Deliver the finalized lessons-learned archive and recommended updates to program standards.
• All critical mobilization facts confirmed or have assigned remediation actions with target dates.
• Open blockers are triaged with documented owners and a short remediation plan.
• Communication channel and cadence for ongoing issue updates is agreed.
• Publish the mobilization confirmation checklist with outstanding items and target resolution dates.
• Circulate the on-site program roster and escalation contacts to stakeholders.
• Present first measurement data
• Establish whether cost variance and milestone adherence are within acceptable tolerances or require remediation.
• Document a prioritized corrective action plan with resolution timelines for the top 3 drivers of variance.
• Set the date for the next follow-up to verify corrective actions are effective.
• Produce a root-cause analysis memo for any metric outside tolerance and circulate to stakeholders.
• Publish a time-bound recovery plan for schedule and cost variances with target completion dates.
• Update the program risk register to reflect newly identified drivers and mitigation owners.
• Outcome comparison vs Outcome Discovery targets
• Documented comparison of 90-day outcomes to Outcome Discovery targets with clear gap descriptions.
• A published lessons-learned summary and a set of practice changes to be applied across the program.
• A triage process and shared channel for warranty and enhancement requests is agreed and scheduled.
• Publish the 90-day outcomes report linking each metric back to Outcome Discovery targets.
• Program-level risk and mitigation review
• Finalize lessons learned and closeout documentation
• Lessons learned workshop
• Root-cause diagnosis for gaps
• Validate mobilization facts
• Warranty and enhancement triage
• Warranty, defects, and enhancement backlog review
• Warranty performance and SLA review
• Agree corrective actions and timeline
• Early adoption and staffing check
• Open issues and immediate blockers
• Enhancement request lifecycle and handover
• Confirm readiness items still open from mobilization
• Agree remediation and closeout actions
• Stakeholder reporting and dashboard timeliness
• Agree next-step remediation actions