EPDM roofing. Details that hold the system together.

Ask the owner for prior drawings, specifications, invoices and any issued coverage documents. Separate a known product identification from a recollection about when the roof was installed. Locate past repairs and equipment changes on a plan. If information is unavailable, say so and identify the investigation needed rather than presenting a guessed assembly as a reliable starting point.

Interview the people who observe the building during leaks or service visits. Record where water appears, which conditions accompany it and what has already been tried. Those observations guide the assessment but do not alone establish entry location or concealed moisture extent. Keep the initial record with later findings so a recommendation can be traced to evidence rather than to the apparent age or color of the membrane.

An adhered membrane, an attachment layer and the structural deck are separate entries in the assembly. Ask what each new layer will meet and how that surface is accepted. Where existing material is retained, document the assessment and any compatibility or condition questions. Where removal is included, define the exposed-condition review and the process for authorizing corrections before the new layers conceal them.

The board and insulation schedule should identify actual products and their role in the selected assembly. Connect any change in roof height to edge, drain and curb details. Ask for the thermal-review basis rather than assuming a standard thickness answers every building’s requirements. Keep substitutions tied to the appropriate assembly review; an apparently similar board may change the interface the membrane or adhesive was specified to receive.

Begin with a roof-plan register of edges, walls, curbs and changes in level. Ask which details apply to each condition and which existing components remain. A general line for membrane installation does not explain every termination. If adjacent construction prevents access, identify the required coordination or unresolved design question before committing to a complete detail scope.

Keep the project attachment basis connected to the actual deck and selected assembly. Product changes or an unexpected substrate can affect more than one detail. Request that accepted revisions be recorded in the final package rather than relying on a verbal field adjustment. The purpose is continuity in the reviewed documents and responsibilities; this notebook does not specify universal fastening patterns, termination dimensions or structural capacity.

Map the equipment that service personnel must reach and note where tools, hoses or replacement parts will travel. Ask whether compatible walkway or protection products are included and how they relate to drainage. Keep separate the roofing scope and any specialist access or fall-protection design. A convenient route across the roof does not establish that the surface or existing detail can tolerate every service activity.

When another trade plans an opening, support or equipment change, request the detail and responsibility before the roof is disturbed. Retain its location, accepted products and any relevant coverage communication. Update the roof plan after the work. This turns a collection of unconnected service visits into a useful alteration history and helps a future assessment distinguish original work from later changes.

Use consistent labels from the assessment through the work and final photographs. Record the boundaries of each completed area and the reason it was included. If further issues were found, connect them to the authorization and final work rather than leaving a separate photo folder with no explanation. A clean-looking finished patch is only one part of a traceable repair record.

At handover, identify existing areas outside the work and the maintenance contact for future observations. Keep any applicable inspection records and actual written coverage. If the proposal involved an additional review or manufacturer decision, save that determination rather than assuming it from a product family name. A repair record should explain exactly what changed while preserving an honest account of what was not investigated or renewed.