A Functional Servicing Report and a servicing brief both explain how a development will connect to water, sanitary and storm systems. A servicing brief is usually shorter and narrower, but the actual difference depends on the municipality’s written requirements.
Typical difference in depth
An FSR commonly combines existing conditions, design criteria, demand and flow estimates, proposed connections, capacity considerations, stormwater strategy and supporting plans. It may also evaluate external works, phasing or agency approvals.
A servicing brief may be appropriate when the project is small, the municipal systems are well understood and only a limited question needs to be resolved. It might summarize connection locations and basic design flows without the full range of modelling, calculations or drawings expected in a larger FSR.
The title does not set the scope
Ontario municipalities use these labels differently. Some combine servicing and stormwater in one report; others request separate documents. A report called a “brief” can still require significant calculations, while a document called an “FSR” may be intentionally functional rather than detailed.
The consultant should translate the pre-consultation record into a deliverable list: systems to assess, analysis limits, drawings, specialist inputs and submission stage. Bous Engineering’s Functional Servicing Report service is scoped against that list instead of relying on the title alone.
Read what an FSR normally contains and how to define a civil engineering consultant’s scope before requesting proposals.
Key takeaway
The practical distinction is level of effort, not vocabulary. Ask the municipality what questions the document must answer and make those requirements explicit in the civil engineering scope.
Bous Engineering supports servicing, stormwater, grading and municipal approval assignments across Eastern Ontario.