Technology Telecom, Media & Entertainment Network Construction & Modernization

Network Deployment

Complex platform, content, and network decisions where revenue, rights, and customer experience intersect.

Example organizations in this space: Ericsson Nokia CommScope Crown Castle

This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.

Inside this journey
  1. Qualification

    Confirm budget, decision authority, timeline, and target markets before committing seller resources.

    Qualification Questions

    Program scale and pilot fit

    • Roughly how many sites do you plan to deploy in the next 12 months? Options: <50, 50–250, 251–1,000, 1,001–3,000, 3,001–10,000, Above 10,000 (likely outside standard scope)
    • Are you prepared to start with a 50-site validation pilot before committing to a full rollout? Options: Yes - ready to proceed, Yes - with specific acceptance criteria to agree, Not at this time, Need to discuss what a pilot would look like

    Target markets and crew coverage

    • Which primary markets (cities, states, or regions) will the initial rollout focus on? Please list the top 3–5.
    • Do you require the seller to guarantee named crew availability or regional crew assignments in those markets? Options: Yes - named/contracted crews required, Yes - guaranteed crew capacity per week, No - open to seller-managed workforce, Not sure yet

    Permitting, seasonality, and constraints

    • How would you characterize permitting risk in your target markets today? Options: Permits usually issued on schedule, Some municipal backlogs in specific cities, Significant permitting delays likely to affect schedule, Unknown - needs assessment
    • Are there seasonal or weather constraints that create hard delivery windows we should know about? If yes, briefly state the months or constraints; otherwise write 'none'.

    Safety, budget, decision authority, and timing

    • Will contractors be required to meet specific safety KPIs, OSHA rates, or carrier safety approvals as a condition of award? Options: Yes - specific KPIs or OSHA thresholds required, Yes - carrier reference checks and program safety approvals required, No specific thresholds, but safety is important, Unsure - will confirm
    • Is there an allocated budget or budget range for this program? Options: Yes - <$1M, Yes - $1M–$5M, Yes - $5M–$20M, Yes - >$20M, No allocated budget yet, Confidential - prefer to discuss in a meeting
    • Who holds final decision authority for selecting a deployment contractor? Options: VP of Network Deployment, Director of Construction, Procurement or Contracts, Cross-functional committee, Other - will provide contact
    • What is your target program start or required live-by date for the rollout? Options: Start within 0–4 weeks, Start in 4–8 weeks, Start in 2–3 months, Start in >3 months - flexible, Specific date - will provide in reply
  2. Outcome Discovery

    Align on deployment targets, constraints (permitting, seasonality), stakeholders, and measurable success signals.

    Discovery Questions

    A quick operational snapshot

    • How many sites are in your 12-month upgrade target that need new construction or permitting? Options: 0-250, 251-800, 801-2,000, 2,001-5,000, 5,000+
    • Give me a quick breakdown of which site types are in scope right now, and approximate percent of the program they represent. Options: Macro tower upgrades, Small cell installations, DAS nodes, Fiber-only handoffs, Shelter/equipment sites, Other
    • When was the last time your internal construction team missed a weekly delivery milestone by more than 10%? Options: Within last month, 1-3 months ago, 3-6 months ago, 6-12 months ago, Over 12 months, Never
    • Describe who on your team signs off on site acceptance and which safety KPIs they require.
    • Which single delivery failure in the last program would have caused you to cancel or delay this rollout? Options: Permit unable to be issued, Power/backhaul not available, Crew safety incident, Major rework due to workmanship, Other

    Where delays translate to real revenue loss

    • If each delayed site costs you a week of revenue, how much monthly revenue does a one-week slip across your program represent? Options: < $50k, $50k - $250k, $250k - $1M, $1M - $5M, > $5M
    • Walk me through the typical permitting hold-ups you've seen in your top three markets.
    • Which stakeholder or authority most often drives the longest permit delays in those markets? Options: City zoning office, Right-of-way / DOT, Utility owners, State environmental office, Private landowners, Carrier approvals
    • How often do seasonal weather constraints compress your available construction window in those markets? Options: Not at all, Occasional short delays, Seasonally significant, months lost, Severe in some markets, Unknown
    • What is the program-wide threshold of weekly missed site deliveries that would force you to change vendors or pause the program? Options: 1-5 sites/week, 6-20 sites/week, 21-50 sites/week, > 50 sites/week, No set threshold

    Crew availability and safety, the choice points

    • Which single crew availability failure would force you to pause the program immediately? Options: Loss of certified tower crews in a market, No available crews for critical weeks, Key subcontractor bankruptcy, Widespread certification lapses, Other
    • How do you currently verify crew qualifications and OSHA incident history before awarding work? Options: Carrier audits and reports, Vendor-submitted records, Third-party safety verification, No formal verification process, Other
    • Tell me about the last safety incident your program recorded, how it affected schedule, and what you changed afterward.
    • To what extent are your carrier contracts prescriptive about acceptable incident rates or mandatory training? Options: Very prescriptive with thresholds, Some mandatory items, flexible otherwise, Minimal or no prescription, I do not know the details
    • Which of these crew constraints worries you most for a fast ramp, finding qualified crews, retaining crews against competitors, or managing certifications? Options: Finding qualified crews, Retaining crews against competitors, Managing and tracking certifications, Scheduling overlap conflicts, Other
    • If a prospective vendor could guarantee named crews in target markets, with carrier-level incident rates, would that remove crew availability as a blocker to signing after a successful pilot? Options: Yes, completely removes blocker, Partially, in some markets, No, other blockers remain, Depends on specific markets

    Permitting and external friction points

    • Who on your team escalates municipal permitting blockers, and where is that process weakest?
    • Which permit types are the longest on average in your markets? Options: Zoning / land use, Right-of-way permits, Electrical/utility permits, Environmental reviews, Utility interconnect approvals, Other
    • Describe any municipal relationships or contractors you already have that speed permitting in priority markets.
    • How many sites are currently delayed by permitting in your active pipeline? Options: 0-50, 51-200, 201-500, 501-1,000, > 1,000
    • What contingency have you used when permits slip, such as provisional power, alternate sites, or phased handover? Options: Provisional power agreements, Alternate site selection, Phased handover to carrier, Construction rescheduling, No contingency used, Other
    • What single permitting failure mode would make you stop a rollout in a market entirely?

    The other paths on your table

    • What alternatives are you actively evaluating right now besides external deployment vendors? Options: Incumbent contractor, Building internal construction capacity, Regional subcontractors by market, Delaying rollout, No alternatives actively considered
    • Are there internal proposals to build and staff a construction workforce instead of using an outside partner? Options: Yes, leadership proposed build-out, Yes, but only for a subset of sites, No formal proposal yet, Undecided
    • List the incumbent vendors or internal teams that currently deliver most of this work, and explain why you might replace them.
    • Rank the following evaluation gates in order of importance when you choose a deployment partner. Options: Safety record and OSHA rates, Reference programs of similar scale, Pilot site results, Crew availability guarantees, Permitting relationships and speed
    • Under what precise condition would you choose to stay with the incumbent or pursue an internal build instead of switching to an external vendor? Options: Incumbent meets schedule consistently, Incumbent cost significantly lower, Internal team can scale to target in 4-8 weeks, No strong reason to change, Other

    Readiness gates and hard limits

    • Name the one readiness item that, if absent, would prevent a pilot from starting within 8 weeks. Options: Permits for pilot sites, Named crews with certifications, Power/backhaul agreements, Clean site data and coordinates, No single blocking item
    • Are APIs or integration endpoints available from your OSS and inventory teams for site transfer and status updates? Options: Yes, documented APIs available, APIs exist but not documented, No APIs, manual transfer only, Unknown
    • Which third-party systems must be integrated for per-site commissioning and status reporting? Options: Carrier inventory system, Backhaul provider portals, Local utility portals, Municipal permit portals, Field reporting app, Other
    • How clean and accessible is the site data we would need, for example power schematics, landowner contacts, and permit histories? Options: Well organized and accessible, Partially complete, needs work, Fragmented across teams, Largely missing
    • Who on your side will be the day-to-day owner for permit releases and site access approvals?
    • Choose one: delay the pilot to fix missing prerequisites, exclude that site class from the pilot, or proceed and accept rework risk. Options: Delay the pilot to fix prerequisites, Exclude the site class from the pilot, Proceed and accept rework risk

    Pilot success signals and acceptance criteria

    • Assuming the 50-site pilot meets schedule, safety, and workmanship targets, what specifically would you need to see to approve rolling to full deployment within the month?
    • List the top five measurable acceptance criteria you would require at each pilot site. Options: On-site completion to approved plans, Safety incident rate below carrier threshold, Schedule variance within agreed window, Successful carrier integration and testing, Documented permit and handover
    • How will you validate carrier acceptance and who signs off on carrier acceptance per site?
    • Which safety KPIs will trigger an immediate stop-work order during the pilot? Options: Lost-time injury, Serious near-miss rate threshold, OSHA-recordable incident, Repeated PPE non-compliance, Other
    • What is the maximum acceptable average schedule variance per site during the pilot before you would consider the pilot failed? Options: <= 1 week, 1-2 weeks, 2-4 weeks, > 4 weeks
    • Would you accept a remediated acceptance plan and proceed if pilot KPIs are met but reference checks note isolated workmanship issues, or would you require additional evidence before contracting? Options: Accept remediated plan and proceed, Require additional corrective proof, Require an extended pilot, Depends on severity and root cause

    Decision makers, contracts, and next steps

    • Who must be at the table to cut commercial and legal terms after pilot acceptance? Options: VP Network Deployment, Director of Construction, Procurement lead, Legal counsel, Carrier program manager, Other
    • How soon after pilot acceptance can your procurement and legal teams execute a master services agreement? Options: Immediately (within 7 days), In 2-4 weeks, 4-8 weeks, Longer than 8 weeks
    • Which commercial term is the toughest to accept right now, payment on acceptance, liquidated damages for delays, or crew availability guarantees? Options: Payment on acceptance, Liquidated damages for delays, Crew availability guarantees, Insurance and indemnity clauses, Other
    • Walk me through the internal process and timeline from pilot acceptance to issuing a purchase order for a rollout.
    • What single governance or contractual obstacle would prevent you from signing within 30 days of pilot acceptance?
  3. Solution Experience

    Walk through how the deployment service will meet the buyer's on-time delivery, safety, and permitting-compression objectives using realistic scenarios.

    Solution Experience

    • Solution Experience Session
    • Confirm the current state and its cost
    • You confirm the demonstrated pilot workflow removes the primary schedule risks you described.
    • Deliver a tailored 50-site pilot schedule, Gantt, and risk register based on the scenarios discussed within 7 business days.
    • You confirm the shown safety KPIs and incident response meet carrier acceptance thresholds you require.
    • Show the consequence on schedule and revenue
    • Provide the list of 50 candidate pilot sites with current permit status, access windows, and any municipal contacts available.
    • Scenario: 50-site pilot under permitting pressure
    • Provide your carrier acceptance criteria and the target safety KPI thresholds to be used in pilot acceptance tests.
    • You confirm the permit-compression tactics and contingency crew plan materially reduce expected permit and crew-driven delays.
    • Scenario: Safety and incident response in-field
    • You agree on the specific evidence and pilot inputs required before a commercial decision.
    • Run the sample pilot staffing model against your target markets and deliver crew availability and cost assumptions.
    • Acceptance and workmanship proof points
    • Validate this maps to your needs
    • Agree next evidence and pilot inputs
    • Solution Experience Session
    • Solution Experience Deck
    • Solution Brief
    • meeting
    • slides
    • document
  4. Solution Scope

    Define modules (site acquisition, permitting, civil, installation, backhaul, testing), responsibilities, acceptance criteria, and out-of-scope items.

    Scope Configuration

    • Site Acquisition and Lease Execution
    • Municipal Permit Filing and Expediting
    • Foundation and Civil Construction
    • Tower Erection and Structural Installation
    • Small Cell Pole and Mount Installation
    • Equipment Shelter and Cabinet Installation
    • Power Provisioning and Meter Installation
    • Fiber Backhaul Trenching and Splicing
    • Antenna, Radio, and RF Equipment Installation
    • System Integration Testing and Network Commissioning
    • Grounding, Bonding, and Lightning Protection
    • Onsite Safety Management and OSHA Compliance
    • Traffic Control and Right-of-Way Management
    • Site Restoration and As-Built Documentation

    Scope Questions

    Site Acquisition and Lease Execution

    • How many candidate sites require lease negotiations in your target rollout (provide a per-market breakdown if possible)?
    • Which lease types do you expect us to pursue for these sites? Options: Ground lease, Rooftop lease, Pole attachment agreement, Easement/right-of-way, Short-term license
    • Do you have existing lease exhibits or site surveys for candidate locations (attach or list document IDs)? Options: Yes, No
    • Specify the minimum lease term and renewal options you require (example: 5 years with two 5-year renewals).
    • Identify any municipal or private landowners who require special negotiation workflows (historical commissions, HOA, airport authority).
    • Are there pre-existing right-of-entry (ROE) or access agreements we must honor before construction (provide permit or agreement numbers if available)? Options: Yes, No, Unsure

    Municipal Permit Filing and Expediting

    • Which authorities having jurisdiction (AHJ) will the sites fall under (city building, county, state DOT, historical commission)?
    • Do any sites sit inside regulated overlay zones (historic districts, downtown cores, airport influence zones) that require Design Review Board approval? Options: Yes, No, Unknown
    • Provide the typical municipal permit backlog or average review time you have experienced in these markets (in weeks by jurisdiction).
    • Which permit application packages should we prepare for each site (choose all that apply)? Options: Building permit, Grading permit, Right-of-way/encroachment permit, Electrical permit, Traffic control permit, Historic review
    • Identify any expedited review pathways or established municipal contacts you expect us to engage for permit compression (provide contact role or permit code where known).
    • Are there template exhibits or supporting studies required with permit filings (photometric, noise, visual simulations, structural engineer stamp)? Options: Yes, No

    Foundation and Civil Construction

    • Which foundation types are anticipated across your site mix (choose all that apply)? Options: Shallow spread footing, Driven pile, Helical pile, Mat foundation, Existing concrete reuse
    • Do you have geotechnical reports or borehole logs for the candidate sites (attach or list report IDs)? Options: Yes, No, Partial coverage
    • Specify any soil bearing capacity or frost depth requirements we must design to (e.g., 2,500 psf bearing, frost depth 40 inches).
    • Identify required civil deliverables per site (site grading plan, erosion control plan, utility locate clearance, as-built topo).
    • Are construction traffic or staging restrictions in effect that impact heavy equipment delivery and foundation pour windows? Options: Yes, No, Varies by site
    • Estimate typical excavation constraints we should plan for (rock removal, groundwater, contaminated soils) and whether remediation is in scope.

    Tower Erection and Structural Installation

    • Which tower types will be part of the scope at identified sites? Options: New self-support tower, Monopole, Guyed tower, Replacement tower on existing foundation
    • Provide the required engineered drawings or stamped calculations we must obtain or verify before erection (tower load study, foundation design).
    • Are crane permits or lane closures required for tower erection in your markets? Options: Yes, No, Depends on site
    • List any tower-specific acceptance thresholds you expect for structural installation (torque spec certificates, NDT weld reports, structural plumb tolerance).
    • Describe required climb-safety or fall-protection equipment and certification standards for crew members on your sites (example: certified fall-arrest training, rescue plan).
    • Do you require third-party structural inspections or tower certification prior to antenna mounting? Options: Yes, No, Case-by-case

    Small Cell Pole and Mount Installation

    • Which pole types and ownership models are expected for small cell sites (streetlight, utility pole, municipally-owned decorative pole, leased pole)? Options: Streetlight, Utility distribution pole, Municipal decorative pole, New private pole
    • Do poles require make-ready work from the incumbent utility or pole owner before installation? Options: Yes, No, Unknown
    • Specify maximum permitted antenna height over roadway or sidewalk and any azimuth/elevation constraints imposed by the municipality.
    • Identify required pole loading or wind-speed calculations and whether a pole-strengthening scope should be included.
    • Are there street furniture aesthetics or color/finish standards the work must meet (attach municipal design guidelines if available)? Options: Yes, No
    • Will utility locates and underground clearance be required for each pole site prior to boring or excavation? Options: Yes, No

    Equipment Shelter and Cabinet Installation

    • Which shelter or cabinet form factors are required across your site types (pad-mounted shelter, NEMA 3R cabinet, micro enclosure)? Options: Pad-mounted shelter, NEMA-rated cabinet, Micro enclosure, Rack inside building
    • Specify HVAC, power distribution, and security requirements for shelters (example: 3kW cooling, rack PDU, door alarms).
    • Do shelters require external concrete pads with specific anchor bolt patterns or prefabricated base rails? Options: Yes, No, Varies by model
    • Provide cabinet interior layouts or single-line diagrams (SLD) if already specified, or indicate if we should propose SLDs. Options: You will provide SLDs, We should propose SLDs
    • Identify physical security acceptance requirements (tamper seals, lock type, fenced compound) and any required access control integration.
    • Are environmental enclosures required to meet any local code or carrier standards (IP rating, NEMA class, fire suppression)? Options: Yes, No, Unsure

    Power Provisioning and Meter Installation

    • Which utility providers or meter vendors service your sites and should be coordinated with for service drops and metering?
    • Do you require permanent metering or temporary construction power for each site (select per-site preference if known)? Options: Permanent metering, Temporary construction power, Both depending on site
    • Provide the single-line diagram (SLD) requirements and main breaker sizes expected for site electrical distribution.
    • Are any sites subject to utility interconnection studies or demand charges that affect provisioning timelines? Options: Yes, No, Unknown
    • Indicate acceptable outage windows for utility connections and whether night/weekend work is permitted for service drops.
    • Do you require power provisioning work to adhere to a specific vendor make/model list for meters or transfer switches? Options: Yes, No

    Fiber Backhaul Trenching and Splicing

    • Which backhaul path types should we provision for your sites? Options: Underground ducted fiber, Direct-buried fiber, Aerial fiber, Dark fiber lease, Microwave
    • Do you have fiber route permits, existing duct reservations, or utility agreements for the planned routes (attach or list route IDs)? Options: Yes, No, Partial
    • Specify required fiber counts and strand assignments per site (example: 12-strand single-mode with 4 active fibers).
    • Are directional drill (HDD) or lane closure permits required for the routes, and do you expect night work to reduce traffic impact? Options: HDD required, Lane closure required, Night work preferred, No special work required
    • What OTDR acceptance thresholds or maximum splice loss limits will validate fiber handover (provide dB loss limits per splice and per link)?
    • Should fiber handover include acceptance artifacts such as OTDR traces, splice logs, fiber ID labels, and cabinet port mapping? Options: Yes, No

    Antenna, Radio, and RF Equipment Installation

    • Which antenna and radio models or part numbers will be deployed, and do you have mounting interface control drawings (ICDs)?
    • Specify required azimuth, electrical downtilt, and vertical placement tolerances we must hit for RF alignment.
    • Are there feeder or coax types and maximum losses you require for site RF design (example: 1/2 inch LMR loss limits, hybrid feeders)?
    • Identify RF safety exclusion zone requirements or public notice processes we must follow during antenna installation.
    • Do you require torque-torque documentation and calibration certificates for antenna mount installations? Options: Yes, No
    • Should antenna alignment be validated with a post-installation RF sweep and recorded azimuth/downtilt report? Options: Yes, No

    System Integration Testing and Network Commissioning

    • What acceptance criteria will confirm a site's network commissioning is complete (for example: power applied, OTDR pass, RF key performance indicators such as RSRP threshold and throughput targets)?
    • Provide the minimum set of test artifacts you expect at handover (commissioning checklist, OTDR traces, RF sweep, throughput test logs, cell ID mapping).
    • Who will execute final network acceptance testing from your side (NOC test team, field RF engineer) and what contact role should we coordinate with?
    • Specify required commissioning KPIs and thresholds for initial acceptance (example: call drop rate less than 0.5%, attached throughput >= X Mbps).
    • Do you require automated test scripts and remote evidence upload to a shared portal as part of acceptance? Options: Yes, No
    • Indicate whether integration testing must include interop checks with a specific backhaul provider or OSS/BSS endpoint and provide required interfaces.
  5. Pilot Evaluation

    Run a 50-site pilot to validate project management, crew availability and performance, schedule accuracy, and construction workmanship against agreed acceptance criteria.

    • success_criteria
    • current_state
    • decision_readiness
    • stakeholders
    • gaps
    • desired_state
    • gaps
    • success_criteria
    • stakeholders
    • desired_state
    • current_state
    • decision_readiness
    • stakeholders
    • decision_readiness
    • current_state
    • desired_state
    • success_criteria
    • gaps
    • success_criteria
    • current_state
    • decision_readiness
    • gaps
    • desired_state
    • decision_readiness
    • decision_readiness
    • decision_readiness
  6. Mutual Commit

    Finalize commercial and legal terms, safety KPIs, reference checks, pilot acceptance outcomes, and ramp-up timelines.

    Agreement Modules

    • Master Services Agreement (MSA)
    • Statement of Work (SOW)
    • Pricing & Payment Schedule (Order Form)
    • Ramp-Up & Mobilization Schedule
    • Pilot Acceptance Report
    • Safety KPI Addendum
    • Insurance & Liability Certificate
    • Performance Security Instrument
    • Reference & Due Diligence Confirmation
    • Change Order & Scope Control Agreement
    • Acceptance & Billing Gate
    • Termination & Transition Plan
  7. Deployment

    Operationalize rollout with readiness checks, execution, and outcome validation.

    1. Pre-Deployment Readiness

      Capture the concrete readiness facts the rollout depends on — permits status, site access windows, municipal contacts, staging yards, and named owners.

      Pre-Deployment Questions

      Environment and site access

      • Is a per-site readiness register (one row per site with site ID, address, named owner, access windows, and permit status) available to the deployment team? (this lets us populate the rollout Gantt) Options: Yes — register already provided, No — register will be delivered by a date (enter below), No — buyer requests seller help to build the register
      • If the per-site readiness register is not yet provided, what date will the buyer deliver it? (so we can schedule site mobilization)

      Permits and municipal contacts

      • Which statement best describes current permit coverage across rollout sites? Options: All permits approved, Majority approved (≥75%), Some approved (<75%), No permits approved, Permits managed centrally by buyer's expeditor
      • Are named municipal contacts or expeditors assigned and available to the deployment team for each jurisdiction? (if yes, indicate 'included in register' or 'separate list') Options: Yes — named contacts provided for each jurisdiction, Partially — named contacts for some jurisdictions, No — buyer expects seller to identify contacts, No — we need seller assistance to secure municipal contacts

      People and ownership

      • Have named owners been assigned for these workstreams: site acquisition, permitting, civil, installation, backhaul, and testing? (we need a named owner to route approvals and escalations) Options: All owners named, Most owners named (≥75%), Some owners named (<75%), No owners named
      • Who is the primary rollout owner who will make schedule decisions and approvals? Provide name, role, and best contact (or enter 'same as register').

      Timing and constraints

      • Are there site-level blackout windows or seasonal constraints already documented per site (e.g., permit hearing windows, nesting seasons, municipal work bans)? Options: Yes — per-site blackout windows documented, No — no blackout windows documented, Some sites only — documentation partial
      • Have staging yards and on-site material storage locations been secured with named contacts for each market (needed to plan crews and truck routes)? Options: Yes — yards secured with named contacts, Partially — secured in some markets, No — buyer to provide when required, Not applicable — deliveries will be JIT/small-cell curbside
    2. Configuration Details

      Lock exact operational parameters the teams will use — per-site power/backhaul specs, crew allocations, permit references, and escalation contacts.

      Configuration Details

      Environments & Endpoints

      • Deployment environment name (enter the exact environment string the build will target; Default: production)
      • Primary operations portal URL (format: https://... — this URL is the target for per-site dashboards and status pushes)
      • Primary rollout region (select the single market scope this configuration will default to; use 'US - state-specific' when you will provide state codes separately) Options: US - national, US - state-specific (enter state codes separately), Canada, EMEA, APAC, LATAM, Custom (enter region code below)

      Technical & Power Specs (values consumed by per-site provisioning)

      • Default backhaul type per site (select the technology the build will provision by default) Options: Fiber, Microwave, Ethernet-over-Copper, Cellular (4G/5G)
      • Default per-site backhaul bandwidth to provision (enter numeric Mbps; Default: 1000)
      • Default power provisioning spec per site (select the electrical spec the build will assume by default) Options: 120VAC single-phase, 208VAC three-phase, 48V DC plant, Customer‑supplied (enter reference ID below)

      Crew, Permits & Escalation (operational parameters used by scheduling, permit filing, and field ops)

      • Default crew size per macro site (enter integer technicians; Default: 4)
      • Default crew size per small-cell site (enter integer technicians; Default: 2)
      • Municipal permit reference ID to use as the canonical permit package identifier (enter the permit document ID, municipal case number, or internal permit-file ID)
      • Primary escalation contact role for site blockers (select the role the workflow will route first) Options: Program Manager, Construction Manager, Safety Lead, Local Project Lead, Field Supervisor, Other
      • Primary escalation contact — Full name and title (enter as a single string: "Full Name — Title"; this is used verbatim in runbooks)
      • Safety incident reporting SLA in hours (numeric; Default: 4 — time from incident to initial report into operations system)
    3. Deployment Execution

      Plan and execute the rollout with integrated Gantt scheduling, per-site owners, milestone tracking, and escalation paths.

    4. Site Acceptance & Safety Gate

      Verify each site's safety performance, workmanship, and carrier acceptance criteria with named sign-offs before handover or billing.

      Checklist items

      • On-site LOTO verification completed
      • Written Permission to Energize / Permission to Operate obtained
      • Site safety inspection report submitted and signed
      • Workmanship QA inspection passed and signed
      • Carrier acceptance test results and sign-off received
      • As-built documentation delivered and acknowledged
      • Punchlist closed or accepted remediation plan approved
      • Site-specific safety KPIs and incident log submitted
      • Formal handover and billing acceptance sign-off received
  8. Success

    Monitor outcomes against success signals, run recurring reviews, and track issues, rework, and enhancement requests.

    Success Reviews

    • Go-live Health Check (weeks 1-4)
    • First Measurement Review (weeks 4-10)
    • 90-day Realization & Remediation Review
    • Quarterly Operational Review

    Issues & Enhancements

    • Set weekly permit-status checkpoints for the top 20 at-risk sites until permit backlog reduces below the agreed threshold.
    • Agree a prioritized burn-down plan for rework and open safety issues with target close dates.
    • Confirm whether current schedule accuracy supports the planned ramp-up or requires a revised timeline.
    • Document any residual gaps that block broad program scale and the specific actions needed to clear them.
    • Publish a prioritized rework closure plan with milestone dates for the next 30, 60, and 90 days.
    • Update the crew allocation plan to close identified throughput gaps and document trigger points for supplemental crews.
    • Circulate a 'lessons learned' brief that captures recurring failure modes and recommended process changes for construction crews.
    • Quarterly metrics review
    • Validate whether quarterly delivery and safety targets in Mutual Commit were met and document any variance actions.
    • Prioritize the top 3 operational improvements to address permit backlog and workmanship hotspots for the next quarter.
    • Ensure the open issue list is reduced and that long-running items have concrete next-step dates.
    • Publish the quarterly metrics pack including the raw data and calculation notes for on-time delivery and safety metrics.
    • Create a prioritized improvement backlog with acceptance criteria and target implementation quarter.
    • Re-confirm success criteria and owners
    • All attendees confirm the documented list of completed, in-progress, and blocked sites is accurate.
    • Immediate remediation tasks documented with owners and target resolution dates ahead of the first measurement meeting.
    • Cadence and escalation paths set for status updates until meaningful outcome data is available.
    • Publish a go-live summary that lists site statuses, named owners, and open issues for async review within 24 hours.
    • Update the per-site issue tracker with remediation tasks and target resolution dates.
    • Schedule the First Measurement Review meeting in the weeks 4-10 window.
    • Present first data against targets
    • Determine root causes for any metric shortfalls and agree concrete corrective actions with dates.
    • Confirm a recovery timeline that puts on-time delivery and safety metrics back on track before the ramp-up milestone recorded in Mutual Commit.
    • Document dependencies and owner commitments required to reach the Pilot Evaluation readiness window.
    • Produce a corrective action plan for schedule and safety gaps with resolution dates and milestone checks.
    • Add a permit-resolution workstream with target dates to address the top-permitted-site backlog.
    • Publish the measurement dataset and calculation method used for on-time delivery and safety metrics for auditability.
    • Outcomes dashboard detailed review
    • Deployment completion review
    • Top failing sites and root-cause actions
    • Persistent issues and backlog review
    • Diagnose root causes for variance
    • Enhancement and process improvement queue
    • Agree corrective actions and timelines
    • Early operational signals
    • Rework and issue burn-down plan
    • Confirm path to acceptance gate
    • Update ramp-up and resource plan
    • Operational commitments and next steps
    • Open issues and immediate remediation
    • Escalation and communication plan
First-Party AI

1-2 minutes please — Your AI agent is working

First-Party AI™ can make mistakes. Always check important information.