# Prepare a comparable sprinkler service brief

Lesson 1 of [Buy and manage sprinkler services](https://firesprinklers.fyi/academy/buy-sprinkler-services.md), 8 minutes.

A service comparison starts before the quotes arrive. Give each bidder the same description of the building, existing fire protection systems, available records and desired work. This lesson offers a purchasing method, not a mandated contract form. Its purpose is to expose assumptions so an attractive headline does not conceal omitted work.

## Describe the system without diagnosing it

Identify the property address and the areas for which you are arranging service. Include the system descriptions used in existing records. Seattle's systems testing page distinguishes automatic sprinkler systems, fire pumps, standpipes and fire alarms in its reporting information. Do not assume that a quote for sprinklers automatically covers every associated system on the site.

If your records are incomplete, mark the uncertainty. Ask whether a preliminary visit is needed to confirm the inventory and service scope. A copied equipment name is useful background; it does not make you competent to decide which technical procedures apply. Ask the provider to explain its assumptions in plain English and identify the records needed to confirm them.

## Ask for a schedule with a basis

Seattle explains that a generally reported test is not the whole maintenance program: secondary tests and periodic maintenance also apply. Use that fact to ask each provider for the tasks included in the proposed visit and tasks managed separately. Ask who will track those other tasks, and what evidence the schedule relies on.

Do not ask every bidder to promise the same generic interval. Ask each to identify applicable local requirements and the system information used. If two proposals disagree, take the disagreement back to the providers or authority. A buyer should resolve the basis of the work before comparing totals, rather than choose the least extensive interpretation because it sounds simpler.

## Include access and coordination

Tell providers who can arrange access and who receives urgent messages. As a recommended operating practice, identify spaces that need tenant coordination and ask how the provider will communicate any interruption. Do not authorize an outage simply by describing a preferred appointment time. Seattle's impairment guidance demonstrates that an interruption can involve notification and mitigation, not just a slot on a calendar.

Ask the provider whether any planned work could affect protection and what local process would then apply. Leave technical decisions with the qualified provider and authority. Record who will coordinate with the owner, alarm company or other affected parties where required. The exact arrangements need to match your site.

## Specify evidence as part of the service

Ask for the service report and an explanation of any incomplete tasks, findings and follow-up work. Where a submission is required, ask who sends it and how you receive evidence. Seattle's local process includes contractor submissions and repair reports, making it a useful example of why documentation belongs in the scope.

Finish with a list of exclusions and open questions. For instance, is corrective work included or quoted later? Are other system types outside this visit? How will missing records affect the proposal? These questions are suggested buyer controls, not claims about standard commercial terms.

Your completed brief should allow a provider to say clearly what it can undertake and what it still needs to assess. Reuse the same brief for every bidder, then update all of them if material information changes. Comparable inputs make differences in scope easier to see.

## Sources

- https://www.seattle.gov/fire/business-services/systems-testing

Also on the [web page](https://firesprinklers.fyi/academy/buy-sprinkler-services/prepare-a-comparable-brief).