Provisional Sum Package Maturity (PCS Gap Analysis) Checklist

Definition: Provisional Sum Package Maturity (PCS Gap Analysis) Checklist helps contractors judge if a provisional sum package is defined enough for instruction, procurement, and execution without assessing subcontractor capability.

Confirms scope, drawings, and specifications are complete and coherent
Verifies approvals, interfaces, and programme logic align with execution
Locks commercial assumptions, testing, warranties, and LD implications
Interactive, commentable, export options with QR code for audit integrity

Start Interactive
Checklist

Provisional Sum Package Maturity (PCS Gap Analysis) Checklist enables a clear, auditable decision on whether a provisional sum package is ready for instruction, procurement, and execution. This package readiness review focuses on scope maturity, design completeness, authority approvals, interfaces, and programme integration, not on subcontractor experience or financial standing. By applying a structured PCS gap analysis, the contractor can avoid scope drift, rework, abortive procurement, late approvals, and programme resequencing. The checklist demands evidence-based confirmation of IFC drawings, coordinated specifications, defined performance requirements, identified temporary works, and clear design responsibilities. It also validates that approval paths are known, submissions are tracked, and timelines align with the baseline programme logic. Commercial clarity is captured through measurable scope, stated assumptions, testing obligations, warranties, and LD implications per approved project specifications and authority requirements. Use this tool to accept instruction, accept with reservations, request clarification, issue a notice of risk, or object to premature conversion. Tick, comment, and export to PDF/Excel with a secure QR.

Drive evidence-based instruction decisions by verifying technical scope, IFC drawings, coordinated specifications, and performance requirements, while ensuring temporary works and builder’s work are explicitly defined and supported by signed matrices, schedules, and transmittals suitable for immediate execution.
Reduce approval and interface risks by confirming authority pathways, submission receipts, conditional approvals, and programme-compatible timelines, alongside signed responsibility and interface matrices, builder’s work drawings, and commissioning roles linked to ITPs and hold/witness points for smooth handovers.
Align procurement and programme by finalising material specifications, identifying long-lead items and fabrication durations, and preparing day‑zero RFQ packages. Validate sequencing, access, and work-front releases so execution can start without negative float or disruptive resequencing of adjacent trades.
Interactive online checklist with tick, comment, and export features secured by QR code. Attach stamped approvals, photos, ITPs, and schedules; then issue a digitally signed decision log to accept, accept with conditions, request clarification, raise risk, or object to premature conversion.

Scope Definition Readiness

1. Confirm the technical scope narrative covers all system boundaries and inclusions; method: review scope matrix against drawings/BoQ/specs; acceptance: zero “TBD/By Others” tags; evidence: signed scope matrix and marked drawings.
2. Verify all execution drawings are issued IFC (or equal) in the DMS; method: transmittal check; acceptance: 100% of key GA, details, and schedules at IFC; evidence: transmittal IDs and revision list.
3. Check specifications are complete and coordinated with drawings; method: spec index cross‑check; acceptance: no conflicting clauses or missing sections; evidence: coordination report and RFI log showing zero open spec RFIs.
4. Validate performance requirements and acceptance criteria are measurable; method: compare Employer’s Requirements to ITP drafts; acceptance: test KPIs defined with units (e.g., kW, L/s, lux); evidence: schedule of performance tests.
5. Confirm temporary works needs are defined where applicable; method: temporary works design brief; acceptance: register approved by the project Temporary Works Coordinator; evidence: approved temporary works register and sketches.

Authority and Regulatory Approvals

6. Identify all required authorities/NOCs; method: approvals matrix; acceptance: matrix lists authority, submission content, and dependency; evidence: signed approvals matrix.
7. Confirm submissions are lodged; method: tracker and portal receipts; acceptance: 100% planned submissions filed; evidence: submission receipts and stamped acknowledgment.
8. Verify approvals/conditions received; method: review letters and stamped drawings; acceptance: critical path approvals in hand or conditions acceptable; evidence: approval letters/NOCs and mark‑ups.
9. Test approval timelines against programme logic; method: link approvals to activities; acceptance: zero negative float and float ≥ 0 days; evidence: programme excerpt with logic ties and notes.

Design Responsibility and Interfaces

10. Allocate design responsibility end‑to‑end; method: RASCI/responsibility matrix; acceptance: designer, checker, approver named per element; evidence: signed responsibility matrix.
11. List specialist design portions (e.g., fire, façade, BMS); method: specialist design schedule; acceptance: briefs and data requirements issued; evidence: issued design briefs and deliverable register.
12. Define interfaces with adjacent trades; method: interface matrix and coordination workshops; acceptance: inputs/outputs, tie‑ins, and tolerances agreed; evidence: signed interface control documents.
13. Confirm builder’s work requirements; method: builder’s work drawings and openings schedule; acceptance: dimensions in mm and tolerances stated; evidence: coordinated builder’s work package and register.

Procurement Readiness

14. Finalize material specifications; method: spec index close‑out; acceptance: product grades, coatings, and standards stated; evidence: approved spec sections and datasheets.
15. Identify long‑lead items and lead times; method: vendor data request and manufacturer confirmations; acceptance: durations (weeks) logged and within programme float; evidence: manufacturer lead‑time letters.
16. Confirm fabrication and shop drawing durations; method: fabrication schedule; acceptance: shop and fabrication windows align with needed on‑site dates; evidence: dated fabrication schedule.
17. Prepare day‑zero RFQ package; method: compile BOQ, IFC drawings, specs, scope notes; acceptance: complete, issue‑ready ZIP; evidence: RFQ checklist and file path.

Programme Integration Readiness

18. Embed package sequencing in the approved programme; method: WBS coding and logic ties; acceptance: activities with predecessors/successors and resources; evidence: baseline extract with activity IDs.
19. Verify predecessor activities complete or scheduled; method: 3–6 week look‑ahead and site walk; acceptance: predecessors have actuals or firm dates; evidence: photos and look‑ahead report.
20. Confirm access and enabling conditions; method: access plan, permits, scaffolds, power; acceptance: dates and capacities aligned; evidence: approved access/permit register.
21. Validate work fronts are released; method: area release register; acceptance: signed area handover with coordinates/levels; evidence: release notes and marked plans.

Commercial and Contractual Clarity

22. Ensure provisional sum scope is measurable; method: measurement rules and QTO; acceptance: BoQ/measurement rules mapped to drawings; evidence: QTO report and mark‑ups.
23. Record pricing assumptions and exclusions; method: assumption register; acceptance: dated, numbered, and approved entries; evidence: signed assumption log.
24. Define testing and commissioning obligations; method: ITP and commissioning matrix; acceptance: hold/witness points allocated; evidence: approved ITP/commissioning plan references.
25. List warranties and durations; method: warranty schedule; acceptance: duration in years and scope per item; evidence: draft warranty forms.

Instruction Readiness Decision

26. Record decision: ready/ready with conditions/not ready; method: digital gate with reasons; acceptance: PM signature and date; evidence: decision log and attached evidence pack.
27. If not ready or conditional, issue formal notice (clarification/risk/objection to premature conversion); method: contract correspondence; acceptance: correspondence ID and recipients; evidence: sent letter and tracker entry.

Make scope execution-ready with coordinated design and evidence

A mature provisional sum package starts with a watertight scope: complete IFC drawings, coordinated specifications, and measurable performance criteria. Use a scope matrix to reconcile drawings, BoQ, and narrative so inclusions, boundaries, and builder’s work are visible and unambiguous. Tag and eliminate “TBD” items early through RFIs, then align acceptance tests with ITP drafts using clear SI units (e.g., kW, L/s, lux, N·m). Temporary works, when applicable, should have a defined design brief and approval by the Temporary Works Coordinator, preventing ad‑hoc solutions that stall site activities. Capture all checks as auditable artifacts: transmittal IDs, coordination reports, RFI logs, and signed matrices. A practical cue that scope is truly execution‑ready is when the builder’s work drawings display dimensions and tolerances in millimetres and the performance test schedule already maps to inspection lots. This completeness enables day‑zero RFQs, accurate measurement, and clean handovers into procurement and planning without scope drift.

Zero “TBD/By Others” tags remain in the scope set
All key drawings are IFC with traceable transmittals
Specifications align with drawings without contradictions
Performance tests list units, methods, and witnesses

De-risk approvals and interfaces before committing the programme

Authority pathways, submission content, and approval conditions must be explicit and time‑linked to programme activities. Build an approvals matrix showing who submits what, to whom, and when. Verify lodged submissions with portal receipts and track conditional approvals or NOCs that gate site work, particularly Civil Defense, municipality, and utilities. In parallel, define design responsibility end‑to‑end and publish an interface matrix stating inputs, outputs, tie‑ins, and tolerances for adjacent trades. Builder’s work should be frozen through coordinated drawings and openings schedules. Testing and commissioning obligations need early assignment within ITPs, specifying hold and witness points. A reliable readiness signal is when approval timelines produce zero negative float and all critical NOCs are either in hand or backed by accepted conditional measures that do not disrupt logic. Collect letters, stamped drawings, and signed matrices so the instruction decision is supported by verifiable evidence rather than verbal assurances.

Approvals matrix lists dependencies and timelines
Conditional approvals are documented and acceptable
Interfaces defined with tolerances and responsibilities
ITPs allocate hold and witness responsibilities

Align procurement and sequencing for a clean instruction decision

Procurement readiness means materials and long‑lead components can be ordered immediately upon instruction. Confirm product grades, finishes, and standards in specifications; obtain manufacturer lead‑time confirmations in weeks; and prepare day‑zero RFQ packs including BOQ, IFC drawings, and scope notes. Check fabrication and shop drawing durations against required on‑site dates to avoid schedule compression. Programme integration is proven when the baseline shows linked activities with clear predecessors, area releases, access and permits, and no negative float if the package starts. Validate work fronts through signed release notes and site photos. Complete commercial clarity by documenting measurement rules, pricing assumptions, warranties, and any LD implications per approved project specifications and authority requirements. When all evidence aligns, issue a signed decision: accept, accept with conditions, request clarifications, raise a notice of risk, or object to premature conversion until gaps are closed.

RFQ pack is complete and issue‑ready
Long‑lead durations fit available float
Work fronts and access are released
Measurement rules map to drawings
Decision is signed with evidence

How to use this PCS Gap Analysis checklist effectively

Preparation: Gather latest IFC drawings, specifications, BoQ, approvals matrix, responsibility/interface matrices, programme extract, ITP drafts, and access/work-front registers. Prepare camera for site photos, laptop/tablet, and PPE for verification walks.
Start the interactive checklist: Open the package record, select this checklist, and enable tick-and-comment mode. For each item, attach evidence (transmittals, letters, photos, schedules) directly in the app.
Cross-verify: For each section, compare entries against the DMS and programme IDs. Flag gaps through comments, assign owners, and set target dates. Link related RFIs or approval submissions where relevant.
Export and review: Generate a PDF/Excel export including comments, attachments, and decision status. Share with the project manager and planner for a coordinated readiness review meeting.
Sign-off and archive: Capture digital signatures from the responsible engineer and PM. Distribute the decision log to stakeholders and archive the QR-authenticated record in the project DMS.

Start Interactive Checklist

Provisional Sum Package Maturity (PCS Gap Analysis)

Call to Action

Start Checklist Tick off tasks, leave comments on items or the whole form, and export your completed report to PDF or Excel—with a built-in QR code for authenticity.

License: CC-BY 4.0. Please credit: “Provisional Sum Package Maturity (PCS Gap Analysis) by Quollnet” with a link to this source page.

Download Excel - Provisional Sum Package Maturity (PCS Gap Analysis)
Download PDF - Provisional Sum Package Maturity (PCS Gap Analysis)
View Image - Provisional Sum Package Maturity (PCS Gap Analysis)

Elie Saad Elie Saad

Apr 04, 2026

FAQ

Question: What makes a provisional sum package “ready for instruction”?

It is ready when scope, drawings, and specifications are coherent; approvals are identified with lodged submissions; interfaces and responsibilities are allocated; procurement can start immediately; programme ties show no negative float; and measurement, assumptions, testing, warranties, and LD implications are documented with verifiable evidence.

Question: How should we proceed if key authority approvals are still pending?

Record the pending approvals and expected timelines, assess float impact, and determine whether conditional execution is acceptable without resequencing. If risk remains, accept with reservations tied to conditions, or issue a formal notice of risk and object to premature conversion until approvals are obtained or timelines align.

Question: Does this checklist replace subcontractor evaluation or prequalification?

No. This checklist evaluates the package’s readiness, not the suitability of a subcontractor. It deliberately excludes capability, staffing, experience, and financial strength. Use your separate prequalification process for vendors, and use this tool solely to decide if the package can be safely instructed.

Question: What evidence should we attach to support the decision?

Attach DMS transmittals for IFC drawings, approved spec sections, approvals/NOCs and receipts, responsibility and interface matrices, ITP extracts, programme snippets with logic ties, access/work-front releases, photos, QTO reports, and the signed decision log. Ensure filenames and dates match the package ID for audit traceability.