The assessment button opens a six-step form. This page remains available as a clear fallback route for browsers, assistive technology and direct links.
Step 1 and 2
Select the closest reason for the enquiry, then mark visible or interior signs such as water staining, dripping after rain, ground-level debris or gutter overflow. There is also an inspection option when no damage is visible. These choices route the context; they do not diagnose the roof.
Step 3 and 4
Provide the postcode and choose the closest building type, then add any known parking, gate, close or occupancy notes. Use the description field for the affected room, timing, weather and previous relevant work. State what you know and leave uncertain causes as uncertain.
Step 5 and 6
Add a name and email address, with a phone number only if preferred. Choose email, phone if supplied, or either as the contact route. The final step asks for agreement to use the submitted data to review and respond to the roofing enquiry.
Preview boundary
This noindex workspace allows the complete modal, validation, progress and responsive layout to be reviewed without sending customer data. Submission delivery remains a launch gate until a real operator, approved recipient, Worker secrets and end-to-end delivery test are in place.
Continue
Practical answers
The route is the site's primary assessment trigger. A full fallback page also exists for direct navigation and accessibility.
No. Live delivery is intentionally disabled until a verified operator and approved recipient are connected and tested.
There are six short steps: concern, observed signs, property, description, contact and privacy consent.
Next step