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:
When a roof opens up during a storm or an ice dam finally forces its way through a membrane lap, the first goal is not a permanent fix, it is stopping water from reaching whatever is underneath, whether that is racking full of product at a distribution center or a production line that cannot get wet. We treat that first response as its own discipline, separate from the eventual repair, because the priorities are different: speed and containment first, permanent solution second.
Two patterns account for most of our emergency dry-in calls around Scranton and Wilkes-Barre. The first is a summer thunderstorm cell that drops wind-driven rain hard enough to find a weak seam or lift a piece of loose flashing, usually on a roof that already had a minor deficiency nobody had gotten around to fixing. The second is an ice dam finally breaking through in late winter or during the spring thaw, after weeks of meltwater backing up under the membrane at a parapet or eave.
Both scenarios usually give some warning if a building has been on a maintenance schedule, but neither one waits for a convenient time. A dam break during a February cold snap and a wind-driven summer storm both tend to hit outside normal business hours, and both need a response that does not wait for the next business day.
The first thing our crew addresses on arrival is not the hole in the membrane, it is what is directly below it. On a distribution floor, that means tarping racking and product before it takes on water, working with whoever is on site to move anything movable out of the drip zone, and containing runoff so it does not spread across the floor to areas that were not originally at risk.
Only once the interior is protected does the crew move to the roof itself to install a temporary dry-in, typically a reinforced tarp or membrane patch secured well beyond the actual opening, since wind can drive water sideways under a tarp that is only sized to the visible hole.
A lot of the buildings we respond to run shifts around the clock, and an emergency call does not mean operations get to pause. We coordinate directly with whoever is running the floor that night, whether that is a shift supervisor at a fulfillment center or a plant manager, to keep the crew's access and the facility's own activity from conflicting.
Where the roof access point sits over active dock doors, we work with the facility to route around them or hold specific doors closed for the short window needed to get equipment up safely. A handful of factors shape how that response actually unfolds once the crew is on site:
The dry-in itself is built to hold through whatever weather is still coming, since a second front is common in the days right after the first one here.
A tarp or emergency patch is not the end of the job, it is what buys time to scope the actual repair correctly instead of rushing it in the middle of an active storm. Once the building is stabilized, we schedule the permanent fix, which might be a straightforward leak repair if the damage is contained, or a larger section replacement if the emergency exposed a wider problem underneath.
Every emergency response gets documented with photos and a written account of what was found and what was done, both for the facility's own records and because that documentation is often what an insurer needs if the event turns into a claim.
Emergency dry-in calls are prioritized ahead of scheduled work, and we coordinate arrival directly with whoever is on site so access is not a bottleneck.
A properly installed emergency dry-in is anchored well beyond the visible opening and built to hold through follow-on weather too, though it is still a temporary measure until the permanent repair is scheduled.
Yes, protecting what is on the floor below the opening is the first priority on arrival, before the crew even goes up to the roof.
We document the damage and the response factually, which supports a claim, but the claim itself and its outcome are between you and your carrier.
The dry-in stops water intrusion immediately with a temporary measure. The full repair, scheduled once the situation is stable, addresses the actual cause so the same spot does not fail again.
A decision-grade Scranton roof record includes interior leak locations, roof access, water paths, membrane and flashing defects, drainage conditions, temporary work, and photographs taken before conditions change. Conditions should be organized by roof area and priority rather than buried in a chronological photo dump. During the visit, the technician should stabilize the immediate opening, protect the occupied area, and document the conditions that still require permanent work. Wide views, detail views, measurements, markings, and interior references make the findings reproducible instead of dependent on memory. Observed facts, recommended actions, completed work, and open items should never share one unlabeled list. Separating them lets an off-site approver see exactly what was authorized and what still needs a decision.
Roof-system identification changes the diagnosis. Around Scranton, the target page inventory includes Spray Polyurethane Foam, Modified Bitumen Sbs, and Modified Bitumen Systems, each with its own seam, flashing, fastener, and compatibility questions. 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. A localized defect may be repairable while saturated insulation or chronic ponding changes the wider recommendation. That is why roof construction and moisture evidence must be connected to what is temporary, what can be repaired permanently, and what requires a broader inspection after the weather clears.
Building operations change how the same roof work is performed. On Insurance Restoration, Food Processing Cold Storage, or Manufacturing Operators, access, interior sensitivity, security, and working hours can define the safe sequence. 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. Wet-weather work may stop at stabilization because permanent materials need a clean, dry substrate and a workable forecast. Daily closeout should state what was opened, completed, and left under temporary protection.
Before pricing becomes the focus, ownership needs an answer to what is temporary, what can be repaired permanently, and what requires a broader inspection after the weather clears. That answer should define the boundary between service work and a capital project. The option matrix should address present failure, remaining risk, investigation still required, installation disruption, anticipated service interval, and future maintenance. Unknown inputs should be visible rather than buried in an allowance. A smaller scope is not automatically prudent, and a larger scope is not automatically safer. The defensible option is the one whose boundaries match the documented condition and the owner's operating requirements.
After this scope, the record should advance to a documented roof inspection once the immediate water entry is controlled. Carrying the same roof-zone names and evidence forward prevents the next visit from starting with an empty file. The record should support both field work and management review. Technicians need locations and prior details; ownership needs priorities, open risk, completed spending, next inspection dates, and a defensible future sequence. 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.
A useful intake for Commercial Roofing of Scranton identifies who can grant access, where water is entering, what operations are affected, whether electrical or ceiling hazards exist, how the symptom changes with weather, and which roof records or photographs are available. Interior photographs can preserve stain limits and active-drip locations before ceiling materials are moved. Roof photographs from facility staff may help with orientation, but they do not replace safe field verification or authorize untrained personnel to enter the roof. 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.
Pricing is easier to evaluate when the scope shows which conditions were measured, which were observed but not opened, and which remain concealed. Unit prices or allowances can address uncertainty without pretending the quantity is already known. 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. When assumptions are visible, the owner can decide whether to investigate further before award or carry a controlled contingency. Either choice is stronger than discovering that two supposedly comparable bids covered different roofs.
Scranton roofs work through seasonal rainfall, wind, rooftop temperature movement, and changing access conditions. That exposure guides the field sequence, but it does not by itself explain active water entry, displaced materials, open seams, punctures, or a storm-created opening. The review should connect the time and location of water entry with roof zones, elevations, drainage paths, and construction transitions. That map helps distinguish one isolated defect from several conditions activated by the same rainfall. A durable scope begins by separating symptoms from causes. Record what was observed, what remains an inference, and what weather, access, equipment, overburden, or concealed construction prevented the crew from confirming.
No. The review should establish what is temporary, what can be repaired permanently, and what requires a broader inspection after the weather clears. 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 interior leak locations, roof access, water paths, membrane and flashing defects, drainage conditions, temporary work, and photographs taken before conditions change. 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.