Sentinel Fire & Safety

Life-safety companies sell recurring, scheduled, documented work to buyers who are managing risk on someone else’s behalf. A property manager choosing a vendor is asking whether the annual testing will actually happen, whether deficiencies will be reported clearly, and whether one company can cover all six service lines instead of four.

Most sites in this sector answer with a dense wall of certifications and a general contact form. The exercise here was to answer with structure instead.

The site is organized as a taxonomy rather than a brochure. Each service line gets an identically structured page, which makes the range legible at a glance and lets a visitor compare two services without re-learning a layout.

A single request process sits across all of them. Whichever service page a visitor starts from, the request form arrives pre-scoped to that service, so there is one process to explain and one inbox to manage.

Every service page runs the same five sections: what the service covers, which properties it applies to, how scheduling works, what happens if a deficiency is found, and how to request it.

Because the template is fixed, adding a seventh service line is a content task rather than a design project — which matters for a company that grows by adding capabilities.

The property-manager section is written for a reader building a shortlist, not a reader who needs convincing that fire safety matters. It leads with coverage across service lines, then scheduling, then reporting.

From there the journey is short: a multi-service agreement summary, a portfolio-level request form that accepts several buildings at once, and a placeholder area for documents a manager may need to circulate internally.

The request form asks for property type, the service required, whether the request is scheduled or urgent, and building access details. That set is enough for a coordinator to book without a preliminary call.

Urgent requests are routed to the phone path immediately rather than through the form, and the distinction is made at the first field so nobody fills in six fields during an emergency.

Six service lines will not fit in a phone-sized menu without help, so the mobile navigation groups them under a single Services entry that expands into a labelled list rather than nesting two levels deep.

The request flow is broken into three short steps with progress shown, because building details are often filled in while standing in a mechanical room rather than at a desk.