Thank you for visiting our site! We noticed you are using a browser we no longer support. To have the best overall experience and avoid issues navigating the site, please click one of the supported browsers to the right to download the latest version for free:
The inspection records membrane, seams, flashings, drains, penetrations, edge metal, moisture indicators, photographs, and practical next steps in a condition report. Most of the roofs we inspect around Scranton and Wilkes-Barre are large enough that a problem can sit hidden for months before it shows up as a stain on a warehouse floor or a drip over a production line. An inspection is how we find that problem on our schedule, in daylight, with the roof dry, instead of finding it during the next storm with a facility manager on the phone.
Every roof in this region takes a beating between December and March that most of the country never sees. Wet, heavy snow sits on a flat roof for weeks at a time, drifts against parapets and rooftop units, and freezes and thaws repeatedly at the edges. The inspection we do right after that season ends is the single most important one on the calendar, because it is the first chance to see what the winter actually did before a spring rain finds it for you.
We walk every drain, scupper, and low point specifically checking for granule loss, membrane stress at drift zones, and any parapet flashing that shows signs of ice having worked underneath it. On buildings with a known history of drainage struggles, we pay close attention to whether this winter's drift pattern matched or shifted from prior years, since that tells us whether an earlier repair actually held.
A second inspection ahead of summer thunderstorm season checks the roof from a different angle: seam integrity, flashing at penetrations, and anything that a hard wind-driven rain off the Poconos would exploit. Between those two key inspections, buildings under a maintenance program get lighter interim checks, mostly focused on drains staying clear and rooftop equipment not having shifted or been serviced in a way that damaged the membrane around it.
Newer distribution buildings along the I-81 corridor tend to need this cycle less for structural reasons and more for drainage housekeeping, since a single roof that size can silt up a drain with debris fast enough to matter after just one season.
An inspection is only useful if what we find gets written down clearly enough to act on later, whether that action is a same-day repair, a budget line for next year, or a claim file. Every inspection produces a report covering the same core items:
Photos are tied to a roof plan location rather than a general description, so a facility manager can hand the report to their own team or to an insurer and point to exactly where an issue sits.
Some inspections are routine. Others are the first step toward a capital decision, and we treat those differently. If an owner is evaluating whether a roof needs a maintenance program, a targeted repair, or a full reroof, the inspection report is written to answer that question directly rather than just listing findings, with a clear recommendation and the reasoning behind it.
We also inspect roofs after specific trigger events rather than sticking strictly to a calendar, including after a wind event strong enough to lift debris, after any hail reported in the area, and before a change in ownership or insurance renewal where the carrier wants current documentation.
Roof access on an active distribution or manufacturing building has to work around your schedule, not ours. We coordinate inspection timing with facility teams so a walk-through does not interfere with dock door traffic or production, and on buildings with rooftop-visible security or safety protocols, we follow whatever sign-in and PPE requirements the site requires.
Drone-assisted photography supplements the physical walk on the largest roofs, mainly to get a full overhead view of drainage patterns and drift zones that is hard to capture from ground-level photos alone, though nothing replaces an actual foot-on-the-membrane walk for finding the small stuff.
Twice a year at minimum here: once right after winter to catch snow and ice damage, and once before summer storm season. Buildings on a maintenance program get lighter interim checks between those two.
Yes, in nearly every case. We schedule around your dock or production activity and stay out of the way of active areas.
We flag it immediately and call the facility manager before finishing the rest of the walk, rather than waiting for the full report to go out.
Yes. Most of our inspection work is on roofs we did not build, and the report is written the same way regardless of who installed the system.
The documentation is factual and photo-backed, which is what an insurer needs to evaluate a claim, though the claim decision itself is always the carrier's call, not ours.
The first conversation about an active leak, repeated service calls, an acquisition review, a restoration decision, an approaching warranty milestone, or a budget that needs defensible roof priorities should establish the Scranton property address, contact on site, roof-access method, affected interior area, when water was first observed, whether entry is active, and any immediate safety concern. The caller should not be asked to diagnose the assembly from the floor. A short description of timing, location, volume, affected equipment, and previous occurrences is more useful than guessing which roof product failed. Clear intake notes reduce wasted roof time and prevent the handoff from losing urgent details. They also create the first event in the roof history that later inspections and repair records can reference.
The owner should see the boundary between the base scope and contingent work. That includes moisture limits, substrate repair, additional layers, damaged deck, blocked piping, inaccessible details, hazardous materials, and work by other trades. Schedule assumptions also belong beside price: weather windows, material lead time, permits, shutdowns, tenant coordination, daily dry-in, and access restrictions. An unexplained low number can become an expensive sequence of changes if these constraints are omitted. A reviewable proposal lets ownership compare boundaries, evidence, materials, quantities, disruption, and closeout—not just totals. The goal is a scope that remains understandable after the salesperson leaves the room.
Weather around Scranton combines seasonal rainfall, wind, rooftop temperature movement, and changing access conditions. The timing of that exposure can reveal a weak detail, yet the weather event and the leak source are not automatically the same thing. Interior evidence should be mapped to a roof elevation before anyone chooses a drain, wall, curb, seam, penetration, or edge as the cause. Water can move laterally through insulation, along deck flutes, or down structural elements and appear away from the opening. This distinction protects the owner from treating a correlation as proof. It also lets the next technician revisit the precise unknown instead of repeating the entire investigation.
The core deliverable is a record of roof-area plans, system and deck information, observed defects, photographs, moisture evidence, drainage, repair history, immediate priorities, budget assumptions, and recommended follow-up. Commercial Roofing of Scranton should be able to hand that record to ownership, a facility manager, or another contractor without a separate verbal explanation. The practical method is to divide the roof into usable zones, compare interior history with exterior conditions, inspect drainage and details, and record defects in a way another decision-maker can follow. Where destructive or electronic testing is proposed, the scope should identify its purpose, limitations, and restoration procedure before work begins. The closeout should identify today's completed scope and tomorrow's unresolved work independently. That structure is especially important when several vendors, tenants, or ownership representatives will rely on the same roof file.
Spray Polyurethane Foam, Modified Bitumen Systems, and TPO 80 Mil can show a similar interior symptom while requiring different investigation and repair details. The observed assembly—not a generic flat-roof label—has to control the scope. Preparation and repair language must fit the substrate. Cleaning, drying, reinforcement, fastening, priming, welding, adhesion, and cure requirements should not be copied from one roof system to another without verification. The final comparison should show which materials can accept repair or restoration, which areas need removal, and which unknowns could change the scope. Product preference comes after those conditions are established.
Manufacturing Operators, Logistics 3Pl, and Healthcare Systems do not share the same interruption tolerance. The roof scope should be written around the occupied property as well as the exterior defect. The pre-work review should locate safe access, occupied areas, shutdown constraints, fire or security procedures, rooftop equipment, pedestrian controls, and interior protection. The building contact should know which decisions are needed before mobilization. A dry-in can be appropriate during active weather even when permanent work must wait. The crew's daily record should identify every temporary edge, cover, ballast, drain protection, and remaining exposure before leaving the property.
The recommendation must answer what needs action now, what can be maintained, what is eligible for restoration, and what belongs in a replacement budget. An isolated repair, repair program, restoration, recover assembly, and full replacement solve different condition patterns and should not be presented as interchangeable price levels. Compare the distribution of wet materials, attachment and deck concerns, drainage, detail density, repair frequency, disruption, expected ownership period, energy goals, code assumptions, and warranty requirements. Cost without those differences is not a lifecycle comparison. This prevents an urgent call from becoming an automatic reroof pitch. It also prevents endless patches from consuming money on a roof whose moisture, failures, or lifecycle cost has crossed a reasonable replacement threshold.
After this scope, the record should advance to a written repair, restoration, replacement, or service-agreement path tied to the inspection findings. Carrying the same roof-zone names and evidence forward prevents the next visit from starting with an empty file. A persistent roof file connects dates, weather, symptoms, findings, repairs, costs, and follow-up. Trends become visible: recurring locations, growing wet areas, drainage issues, or a rising frequency of unrelated failures. Commercial Roofing of Scranton can keep inspection and maintenance active while repair, restoration, or replacement moves through a separate project opportunity. The path remains response, evidence, the right scope, closeout, and the next scheduled roof decision.
No. The review should establish what needs action now, what can be maintained, what is eligible for restoration, and what belongs in a replacement budget. Replacement becomes a defensible recommendation only when the field evidence, moisture, assembly condition, repair history, deck or attachment concerns, and lifecycle comparison support it.
It should document roof-area plans, system and deck information, observed defects, photographs, moisture evidence, drainage, repair history, immediate priorities, budget assumptions, and recommended follow-up. It should also label temporary and permanent work separately, state assumptions and exclusions, and identify the inspection or service step that follows the current scope.
The immediate visit creates the first roof-area record. A follow-up inspection establishes condition and priorities. Completed repairs, recurring observations, drain service, warranties, and future recommendations are then retained so maintenance stays scheduled and larger work can be placed into the appropriate capital year.
From service call to roof plan
Stabilize the problem, document the roof, compare the viable paths, and keep the resulting roof history active.