← Whole-system mapRecords and requirements

Verify Poly-B Permit, Inspection and Insurance Records

Permit and insurance questions are address- and scope-specific. Build a dated record of who was asked, what was confirmed and which documents are expected at completion.

  1. 1

    Identify the authority from the property address

    Determine whether the property is in Coquitlam, Port Coquitlam or Port Moody before relying on a permit page or application process. Similar project names do not create one regional permit route. Record the civic address, property type and concise proposed scope when contacting the municipality. Coquitlam describes an electronic plumbing permit process; Port Coquitlam and Port Moody publish their own plumbing and renovation information. Keep the dated response or application reference with the project file so later decisions can be traced to the correct authority.

    Confirm the municipality from the civic addressDescribe the proposed plumbing scope accuratelyRetain dated authority responses
  2. 2

    Ask about permits before finalizing the schedule

    Confirm whether the proposed alterations require a plumbing permit, a related building permit or another review, and ask who may apply. Do not treat general website information as project approval. Record required drawings, contractor information, fees, inspections and any dependencies between applications. If the scope changes after openings or design review, ask whether the permit record must be updated. Put these steps in the schedule before piping is concealed or finishes are restored, because an inspection cannot be assumed to fit after every access opening has closed. Confirm the applicant before comparing permit-administration allowances. Coquitlam currently distinguishes homeowner submissions from contractor applications for certain residential work: an owner-applicant needs a digital drawing, while its contractor instructions identify specified residential categories that do not need one. Ask the City which route and documents apply to the actual repipe. This is not a waiver of permits, professional design or inspection. Keep this Coquitlam document distinction separate from Port Coquitlam and Port Moody requirements, and record who prepares and submits the accepted package.

    List required applications and applicantsPlace inspections before closureReconfirm requirements after material scope changes
  3. 3

    Build a contractor and product file

    Keep the written estimate, contractor identity, applicable licensing or qualification information, insurance documents requested for the project and current product literature for proposed piping and fittings. Ask the contractor to state the system boundary, connection methods, testing and warranty terms in writing. These records do not replace municipal approval, but they let the owner compare the proposed system with the permit and final installation. For strata work, also record council authorization and any site-specific contractor requirements imposed by the corporation.

    Retain the signed scope and approved changesCollect current product documentationRecord project-specific contractor requirements
  4. 4

    Keep insurer communication factual and dated

    Contact the appropriate insurer or broker with accurate property and scope information, then retain the questions asked and written responses. A website cannot predict eligibility, coverage, premium or claim treatment, and a contractor estimate is not an insurance decision. If photographs, invoices, permits, inspection results or completion statements are requested, add them to the closeout checklist. Separate current-policy questions from construction insurance and contractor-liability records so each document has a clear purpose and owner.

    Do not infer insurance outcomesRetain written questions and responsesList requested completion evidence
  5. 5

    Document inspections and concealed work

    Schedule applicable municipal inspections and contractor testing at the correct construction stage. Before closing access, photograph completed routes and connections where safe and permitted, using labels that match the fixture and branch map. Record inspection dates, results and any correction or reinspection. Do not describe a project as inspected unless the relevant record supports that statement. If part of the work is outside a permit or inspection scope, distinguish it clearly instead of using one approval to imply review of every finish, fixture or concealed condition.

    Match photos to branch and room labelsRetain inspection and correction recordsAvoid overstating the scope of an approval
  6. 6

    Assemble the completion package

    Create one file containing the final scope, permit documents, inspection records, approved changes, invoices, product information, warranty terms, testing records, photographs and restoration sign-offs. Add shutoff labels and a simple route map for future maintenance. Where an insurer, lender, buyer or strata corporation requests specific evidence, include it without representing that the package guarantees acceptance. Note excluded, inaccessible or deferred branches so the record remains accurate. Store copies where the property owner and authorized building representatives can retrieve them.

    Index documents by date and purposeInclude approved changes and exclusionsKeep the final route and shutoff map
  7. 7

    Recheck records after any scope change

    Concealed conditions can change routes, openings or fixture work. When that happens, document the discovery, obtain a priced written change and confirm whether municipal, strata or insurer records also need revision. Keep the original decision, the change and its approval together. Use the whole-home scope and access pages to update technical responsibilities, then return to the quote-comparison page to preserve a consistent cost record. A current file is more useful than an initial checklist that no longer matches the work actually performed.

    Link every change to evidence and approvalReconfirm permit or inspection impactsUpdate the final scope before closeout