Work Package Coordinator

Equal Opportunities Statement

At United Infrastructure, we are committed to making every interaction a positive and inclusive experience. If there is anything we can do to support you, remove barriers, or make the process more accessible, please let us know — we want this to be the best possible experience for you.

Role purpose

To provide end-to-end package controls for Access / GI / PRI by coordinating access readiness, controlling information/deliverables planning (MIDP), and tracking deliverable submissions and acceptance through disciplined registers, evidence packs, and review-cycle management. The role will extend into Part B to support compilation of completion/handover documentation as construction progresses.

Roles & Responsibilities

1. Access readiness coordination (W3-driven) – Own and maintain the W3 access request workflow for assigned work packages. Prepare and submit complete access request packs by coordinating required inputs, including condition/track surveys and photo records, ecology requirements (ECoW/ACoW constraints, pre-works checks, watching brief needs), utilities records and any verification requirements (trial holes, protection measures), land access/wayleave status and constraints, traffic management / streetworks / permit requirements (where applicable), temporary works dependencies (where access relies on TW solutions). Maintain an Access Requests Dashboard showing status, blockers, owners and target dates. Enforce a “Definition of Ready” standard before requests are escalated (no incomplete packs).
2. Package scope control and demarcation support – Support the PM/Interface Manager by maintaining package scope sheets: scope, boundaries, demarcations, assumptions/exclusions, interfaces, and acceptance route. Ensure that scope gaps/overlaps are identified early and recorded as actions/decisions.
3. MIDP coordination and information management – Build and maintain the MIDP (who issues what, when, in what format, via what system). Align MIDP dates to the master programme and subcontractor schedules (Akela/Story/Sweco/Fairhurst etc.). Maintain the Inputs Register (survey/LiDAR/utilities/GI outputs/speed data/land plans) including version control and coverage limits. Proactively chase missing inputs and ensure any gaps are raised early via TQ / action and visible to the delivery team.
4. Deliverables tracking (DAR/PDR and submissions control) – Own the package Deliverables Register (PDR/DAR extract) and track all deliverables from subcontractors through draft -> submission -> review -> acceptance / close-out. Track and report planned vs actual issue dates, revisions, acceptance status, and dependencies. Ensure deliverables are issued under proper document control with correct metadata, transmittals, and filing.
5. Submission evidence packs (Part A focus) – Compile and maintain a standard submission evidence pack for key deliverables (GI and design), ensuring each submission includes, as applicable: correct revision-controlled deliverable(s), check/approval evidence (designer QA sign-off; UI check where required), assumptions/departures log, inputs references (survey/LiDAR/utilities/GI factual outputs versions), comment tracker / response log (where applicable), formal transmittal reference and register update. Ensure packages are “audit-ready” for acceptance discussions with SSE and authority submissions support.
6. Review-cycle and actions management – Operate comment trackers and enforce agreed review rules (e.g., single consolidated response, timeboxed reviews, resubmission dates). Chair package working sessions as required; issue minutes, actions, and decision logs. Drive action closure with evidence and elevate blockers early.
7. Programme integration support (hold points and logic) – Support the PM/Interface Manager by ensuring package activities reflect hold points (land access, ecology licensing, permits/streetworks, RCC/authority submissions), handoffs (GI -> design; design -> submission; submission -> acceptance), milestones required for Part A delivery. Maintain a 2-6 week lookahead for assigned packages, highlighting upcoming approvals and blockers.
8. Part B extension – completion / handover readiness (future scope) – As the project transitions into Part B, expand the evidence-pack approach into completion/handover packs, including as-builts, inspection/test records, ITP/NCR close-out, permit close-out / reinstatement records, environmental compliance evidence, temporary works close-out documentation, handover documentation required by the client.
9. Reporting and assurance – Provide weekly reporting to PM/Interface Manager covering W3 access request status and blockers, MIDP compliance and upcoming information releases, deliverables status (DAR/PDR), review cycle progress, and acceptance forecast, risks/issues/decisions required.

#J-18808-Ljbffr…