Core samples & roof composition
Keep selected core-sample observations with their location, roof area and supporting photos. Confirm the applicable native form and required information for the released inspection.
A structured way to collect commercial-roof observations, test findings and photos, with the roof plan and inspection objectives close at hand.
Start with the roof areas, assets and known conditions. Define the inspection targets and the observations or tests needed at each location. The existing Field workflow uses a released packet and assigned personnel to keep that work in context.
Field results and photos stay linked to the target and roof. Technical review checks the evidence before it is used in the report and scope.
The existing workflow connects planned targets, assigned field work, verified photos and technical review. Device operation, required test forms and company access are confirmed before pilot use.
Roof areas, inspection objectives, mapped targets and the current source revision.
Release the appropriate packet to authorized field personnel. Keep field access separate from estimating, financial and administrative access.
Record what was actually found, retain unknowns and explain changed target locations where required.
Verify photo completion and review results before relying on them in scope or reporting.
Guide consistent data collection while retaining the judgment of the inspector and reviewer.
Keep selected core-sample observations with their location, roof area and supporting photos. Confirm the applicable native form and required information for the released inspection.
Organize moisture-probe and impedance-related observations at the test location. Record what was measured; thermal patterns alone do not establish moisture.
Connect visual observations and photos to roof assets, details and deficiencies, instead of leaving them as disconnected images.
Use suitable site imagery and mapped targets to help the team understand where work is needed. Aerial Intelligence is optional and has its own access and processing requirements.
Existing packet and company job-access controls define who may view, capture and submit. Broader multi-inspector coordination is part of the pilot qualification, not an unrestricted collaboration promise.
Reviewed observations and verified originals support the existing Report, QA and Scope workflow. Capturing or uploading a photo does not itself approve a finding or release a report.
The Field App and guided inspection are part of the Roof Man OS story. Confirm assigned job/roof access, the released checklist, capture/import, upload completion and interruption recovery on the actual pilot devices before using them as a dependable jobsite workflow.
Core estimating and ordinary project work do not require a drone. Field observations still require appropriate site access, competent testing and professional review.
We’re introducing Roof Man OS to a small group of commercial roofing contractors. Tell us how you work.