FSR Addendum vs Revised Report in Ontario
An FSR addendum vs revised report decision starts with the changed engineering question. For a servicing report revision, an FSR change log connects each change to its supporting evidence. A supplement may depend on an earlier report, while a revised issue can consolidate the current assessment. Confirm the proposal, affected assumptions and reviewing authority’s requirements before choosing the format. This Ontario guide explains how to build a clear baseline, track replacements and coordinate the report with drawings. Local submission requirements still govern the actual project.
- Identify the baseline and its limits.
- Trace changed inputs through the assessment.
- Confirm the required supplement or revised-report format.
- Issue one coordinated document package.
Conceptual workflow; neither format is automatically accepted.
FSR addendum vs revised report: start with the changed servicing question
An FSR addendum supplements an identifiable functional servicing report. A revised report presents an updated report issue, bringing the affected discussion, calculations and references into that issue. Neither title, by itself, tells a reviewer whether the engineering assessment is complete. The useful question is which package will explain the current proposal clearly, preserve the necessary evidence and meet the reviewing authority’s requirements.
There is no general rule in this guide that a small development change qualifies for an addendum across Ontario. The engineer must assess the change, and the responsible authority may require a particular submission format. A short attachment cannot make conflicting baseline assumptions disappear. Equally, renaming an old report “revised” does not establish that its analysis has been updated.
This guide explains the document-control decision rather than repeating how to prepare an entire FSR. It is for owners and project teams assembling a resubmission, reconciling review comments or deciding what information to give their engineer. It does not determine municipal acceptance, reserve servicing capacity or replace a project-specific engineering scope.
FSR addendum vs revised report: what changes?
An addendum normally depends on another document. The reader needs to know exactly which report it supplements, which sections remain applicable and what it replaces. That dependency is central to the decision. If the original report is unavailable, has several competing issues or contains conclusions that the attachment contradicts without resolving, a short addendum may create a longer review task.
A revised report can consolidate the current assessment into one principal document. However, consolidation still requires a clear revision record. The reviewer should not have to compare every page against an earlier issue to discover what changed. Supporting calculations and drawings may remain separate files, provided their relationship to the current report is explicit.
A technical memorandum is another document label, not an automatic alternative approval route. It might explain a narrow question, record an engineering assessment or respond to a review comment. Whether it can satisfy a specific submission requirement depends on its contents and the authority’s expectations. Decide the required evidence before selecting the title.
Trace changed FSR inputs across the document set
| Question | Addendum approach | Revised-report approach |
|---|---|---|
| Where is the current assessment? | Across the identified baseline and supplementary material | In the revised principal report and its referenced supporting documents |
| What must the reader reconcile? | Retained sections, replacements and any changed conclusions | The revision summary and the current coordinated evidence |
| What can go wrong? | Old statements remain apparently valid beside conflicting new ones | The new issue date conceals unchanged or unsupported analysis |
| What decides suitability? | Engineering scope, document clarity and the responsible reviewer’s requirements—not page count alone | |
FSR addendum vs revised report: establish the baseline
Start with the report that the current application actually relies on. The most recently modified file in a shared folder is not necessarily that report. Collect its cover, complete appendices, drawing list and submission correspondence. Check whether later material already supplemented it. An isolated PDF attachment may omit the very calculation or response that explains a conclusion.
Create a simple baseline register. Give each record its title, author or issuing organization, issue date, revision identifier, purpose and known submission status. Include the current site concept, servicing drawings, relevant survey information, review comments and previous responses. Distinguish records received from records still requested. A filename should help locate evidence, not substitute for checking the document itself.
Then establish what the baseline describes: development uses, relevant quantities, phase boundaries, proposed connections, drainage arrangement and infrastructure assumptions. Do not recreate engineering calculations from a planning summary. Ask the engineer which source documents supplied those inputs and whether the underlying records remain suitable for the current assessment.
Where several report versions circulate, avoid silently choosing one and discarding the others. Preserve the record and resolve which issue governs the proposed update. The new package can then identify its relationship to that issue. This is especially important when a previous addendum changed only one discipline or when review comments refer to an earlier drawing revision.
FSR addendum vs revised report: trace each change
Prepare a factual list of proposal changes before deciding whether the update is “minor.” A changed building outline might leave some demand assumptions unchanged but affect a service route, drainage area or access needed for infrastructure. A similar unit total might conceal a different use mix. The engineer’s task is to determine the consequences, not merely repeat the owner’s description of the change.
For each change, identify the affected input, the analysis that uses it, the drawing that communicates it and the conclusion that depends on it. This creates a practical chain from proposal to evidence. It also exposes questions that need another consultant’s input. Do not mark a technical effect as absent simply because it is not visible on an architectural drawing.
Compare the changed inputs and affected documents
| Changed item | Questions for the engineering review | Documents to reconcile |
|---|---|---|
| Development statistics or use | Do the existing demand assumptions still describe the proposal? | Planning statistics, report inputs and applicable calculations |
| Water servicing arrangement | Have connection assumptions, supporting information or the assessed arrangement changed? | Water analysis, records and servicing drawings |
| Sanitary connection or loading | Does the assessment still address the proposed discharge and receiving system? | Demand calculations, capacity evidence and connection details |
| Drainage or surface layout | Are the drainage areas, controls and related assumptions consistent? | Stormwater report, drainage plans and grading information |
| Phasing or external works | Can the stated servicing approach operate in the proposed sequence? | Phase plans, infrastructure dependencies and implementation discussion |
| Authority information | Does new direction or data alter the assessment basis? | Current correspondence, referenced records and response log |
The table is a coordination aid, not a calculation method or a mandatory municipal template. Not every project needs every listed investigation. The responsible engineer should identify the applicable work and explain any exclusions. Where a conclusion depends on pending information, label that dependency rather than writing an unconditional statement.
FSR addendum vs revised report: a bounded supplement
An addendum may be a useful format to discuss when the assessment has a clear baseline and a genuinely bounded update. The retained material must remain intelligible and relevant. The new document should identify what it examines, what evidence changed, which findings follow and which earlier statements it replaces. Its usefulness depends on making the complete assessment easier to understand.
For example, the engineer might be asked to address a specific reviewer question using confirmed information while the development proposal remains unchanged. That does not automatically make an addendum acceptable, but it gives the team a defined scope to discuss. If the investigation reveals wider effects, the proposed document format should be reconsidered rather than protected for convenience.
A credible addendum needs more than a sentence saying that all other conclusions remain valid. The engineer should establish the basis for retaining them within the agreed review scope. Identify relevant boundaries: which systems were examined, which documents were compared and what information remains outside the assignment. Readers should not mistake a targeted assessment for a fresh review of every engineering discipline.
Consider the reader’s workload as well. One concise supplement to a clear report may be manageable. Several attachments that repeatedly supersede one another can become difficult to follow. There is no numerical threshold in this guide; the practical test is whether the reviewer can identify the current evidence without reconstructing an undocumented history.
FSR addendum vs revised report: when consolidation helps
A revised report may offer a clearer route when changes affect multiple chapters, calculations or conclusions. The issue is not simply that the proposal became larger. It is that the current assessment may no longer be understandable as an unchanged baseline plus a limited exception. Consolidation lets the engineer present the proposal and its supporting evidence as a coherent issue.
Warning signs include inconsistent development statistics, changed infrastructure assumptions, repeated replacement appendices and a drawing list that no longer matches the assessment. Another warning is a conclusion that remains on the original report’s closing page even though a later attachment qualifies it substantially. These conditions deserve an explicit document-control decision.
Consolidation does not mean erasing the audit trail. Preserve prior issued records in the project archive, provide an intelligible revision summary and identify the current submission set. The revised report should distinguish updated analysis from retained information. A fresh cover date is not evidence that all source data were refreshed or that every earlier review comment was resolved.
The authority may also prescribe a revised report regardless of the team’s preferred format. In that case, confirm the required scope and issue conventions with the engineer and reviewer. Do not promise that a comprehensive-looking document will secure approval. Document completeness, engineering adequacy and the authority’s decision remain separate matters.
FSR addendum vs revised report: build a useful change log
A useful change log connects the reason for a change to the resulting evidence. “Updated as requested” is usually too vague for internal coordination. State the relevant comment or changed input, identify the affected section and point to the new analysis or drawing. The log should help a reader find the answer without replacing the technical explanation.
For a targeted supplement, include a retained-or-replaced field. State whether the entry adds information, replaces a specific passage or appendix, or changes a conclusion. Avoid broad statements that unintentionally supersede unrelated work. If an older figure remains useful only as background, make that distinction visible.
- Trigger: the review comment, changed proposal or new information prompting the work.
- Baseline reference: the exact report section, appendix or drawing issue affected.
- Assessment: the work undertaken within the agreed engineering scope.
- Current evidence: the new section, calculation, drawing or referenced record.
- Effect: the resulting change, supported retained conclusion or unresolved question.
- Responsibility and status: who must provide any outstanding input and how closure will be established.
A “no change” entry can be valuable when it records a reasoned comparison. For instance, the engineer may confirm that a particular input remains the same after checking the coordinated proposal. Do not extend that finding to other inputs automatically. Unchanged demand statistics do not, on their own, establish unchanged drainage or connection conditions.
Keep the owner’s action list separate from the technical conclusion where necessary. “Request current drawing” is an action; “drawing reviewed and consistent with the report” is an outcome requiring evidence. Combining the two can make an unfinished package appear complete during a hurried submission check.
Coordinate the FSR addendum with drawings and related studies
An FSR update rarely exists in isolation. Its development inputs may come from planning or architectural material, while its infrastructure discussion must agree with civil drawings and related studies. Establish which coordinated issue the engineer is assessing. If another team member changes that issue during the review, identify the change before the report is finalized.
Check development statistics in more than one location. Covers, executive summaries, calculation tables and conclusions can retain different figures after an update. Check phase names and connection labels as well. A package can be technically detailed yet difficult to review if the same system has different names across its files.
Where a separate stormwater report supplies part of the assessment, identify that document and its current issue. Do not imply that revising the FSR automatically revises the stormwater analysis. Likewise, a servicing drawing may communicate the proposed arrangement without establishing every capacity assumption discussed in the report. Each document has a role.
Elmid’s site servicing plan and stormwater management report services address related engineering deliverables. Confirm the specific coordination scope for the project rather than assuming that an FSR update includes every design drawing, investigation or approval response.
FSR addendum vs revised report: handle missing information
An update may depend on records that are not yet available: a confirmed concept, relevant infrastructure information, specialist analysis or a reviewer’s clarification. Record the missing input and the conclusion it affects. This is more useful than a general disclaimer at the end of an otherwise unconditional report.
The engineer can then decide what work can proceed and what must remain provisional. A draft coordination package may help the team resolve inputs, but it should not be confused with an issued submission. Use document status consistently so that a preliminary file does not become the apparent final assessment merely because it was attached to an email.
Agree on a coordinated input set before final issue. This does not prevent later design changes; it establishes what the assessment actually considered. If the proposal changes after that point, return the changed information to the engineer. Do not alter technical figures independently to make the report appear to match a newer drawing.
Changing consultants does not eliminate the need for a clear scope
Sometimes a new engineering team receives the earlier report. Provide the complete record, including appendices, review comments and known later submissions. Explain what the new team is being asked to do: review a particular issue, prepare an updated assessment or coordinate a broader resubmission. These are different assignments.
The new engineer should determine what information can support the work and what requires checking or replacement. Do not assume that possession of a signed PDF permits another person to edit its conclusions or represent the original author’s work as newly verified. Resolve authorship, responsibility and permitted use through the project’s professional arrangements.
For professional-practice questions, consult the applicable current guidance or seek advice through Professional Engineers Ontario’s practice-advice resources. This article does not interpret contractual rights, reliance arrangements or legal obligations. Those questions should be directed to the appropriate professional rather than inferred from a report filename.
Two hypothetical examples show why the label comes last
Example one: a clarification that stays within a defined assessment
Imagine a project with an identifiable issued report, consistent current drawings and one outstanding reviewer question about the source of a stated input. The owner supplies the requested record, and the engineer checks its relevance. The review finds that the proposal and assessed arrangement remain as described, while the explanation needs to be made clearer.
The team can discuss a targeted supplementary document with the reviewer. Such a document would identify the baseline, explain the question and evidence, and state the effect on the assessment. It would not claim that the entire project received a new approval. If the reviewer instead requires the clarification incorporated into a revised report, that instruction governs the submission format.
Example two: an apparently small change affects several dependencies
Now imagine a project that retains a similar overall development scale but changes phase boundaries and the location of a proposed servicing connection. The owner initially asks for a short addendum. During review, the engineer identifies that the interim arrangement, drawing references and parts of the receiving-system assessment need reconsideration.
The decision should respond to that expanded scope. A coordinated revised report may communicate the current proposal more clearly than several exceptions to the old one. Related studies or drawings may also need updates within their own scopes. The team should resolve the required evidence and reviewer expectations before promising a document length, fee or submission date.
Both examples are hypothetical coordination scenarios, not completed Elmid projects or statements about a particular municipality’s acceptance policy. Their lesson is that the engineering implications and review requirements determine the package—not the owner’s initial description of the change.
FSR addendum vs revised report: review the response package
Before issue, follow one important comment through the package as if you were seeing it for the first time. Find the comment, the response, the report location and the supporting drawing or calculation. If that route ends at an earlier issue or an unexplained statement, resolve the gap. This exercise tests traceability without pretending to repeat the technical assessment.
Next, read the current conclusion without looking at the change log. Does it describe the same development, systems and qualifications as the body? An update can leave the conclusion too broad even when individual sections are accurate. Return any inconsistency to the responsible author rather than editing a technical conclusion informally during document assembly.
Separate a response from a closed comment
A team can provide a reasoned response without knowing whether the authority considers the comment resolved. Use statuses that reflect the evidence: response prepared, submitted, clarification requested or resolution confirmed. Avoid using a green tick for all four. Where the reviewer asks a follow-up question, retain the exchange so that the next issue addresses the actual remaining concern.
If a response relies on a future drawing change, identify that dependency. The report should not describe the drawing as coordinated before the revised issue exists and has been checked. Similarly, a promise to obtain missing infrastructure information is not the same as assessing that information. Keep commitments visible until the supporting work is available.
Check whether the package can stand on its own
A reviewer should not need an undocumented phone conversation to understand which report sections remain operative. Include the necessary explanation in the issued material or its clear references. If the explanation requires repeatedly saying “ignore that paragraph and use this later email,” discuss consolidation with the engineer. The objective is a dependable current record, not the smallest possible attachment.
Finally, distinguish document preparation from submission authority. Confirm who is assembling the application, who is issuing the engineering material and who is communicating with the reviewer. A coordinated distribution list helps prevent one participant sending a preliminary file while another sends the final set. Preserve the actual issued package, not just a folder that continues to change after submission.
Package a revised functional servicing report for resubmission
Prepare a submission index identifying the principal report, supplementary documents, drawings and responses included. Use consistent titles, dates and revision identifiers across the index and the files. If the package replaces earlier material, say which material. Avoid vague labels such as “latest final” that become meaningless when another issue follows.
Before sending, open the actual files being submitted. Confirm that appendices are present, references point to the intended issues and the response log identifies supporting locations. Check that an earlier attachment has not been copied into the new package by mistake. These are document-quality checks; they do not replace the engineer’s technical review.
After submission, preserve the issued set and delivery record. Record the authority’s acknowledgement separately from its technical review. A successful upload or receipt email establishes delivery, not acceptance of the servicing conclusions. When comments arrive, connect them to the submitted issue so the next response does not inadvertently address an obsolete package.
What to send Elmid for an FSR revision discussion
Send the complete earlier report, the current proposal and the full relevant review comments. Include known addenda, previous responses and the drawings referenced by the assessment. Describe the changes factually and identify unresolved inputs. If the authority has requested a particular document format, include the complete instruction rather than a shortened summary.
Elmid Design Inc.’s functional servicing report service can be discussed in relation to the project’s engineering needs. Agree on the review boundaries, required analysis, coordinated deliverables and responsibilities before treating an update as a defined assignment. Municipal acceptance and infrastructure decisions remain outside an article’s promises.
A useful initial outcome is a scope decision: what can be retained, what needs assessment, which inputs remain missing and how the resulting evidence should be presented. That decision is more valuable than choosing “addendum” because it sounds shorter. It also provides a clearer basis for discussing fees and timing without making unsupported promises.
Frequently asked questions
Is an FSR addendum always acceptable for a minor change?
No. “Minor” is not a universal submission category established by this guide. The engineer must assess the implications, and the responsible authority may specify the required format. Confirm both scope and format for the actual application.
Does a revised report mean every calculation was redone?
Not necessarily. Read the revision summary, scope and supporting evidence. The report should explain the current assessment and distinguish updated work from retained information. An issue date alone cannot establish the extent of the review.
Can a change log replace the engineering analysis?
No. A change log helps locate and explain the work. It should point to the analysis, drawings or records supporting a response. It cannot make an unsupported conclusion adequate merely by listing it as completed.
Does an FSR expire after a fixed period everywhere in Ontario?
This guide does not establish a province-wide expiry period. Review the applicable authority requirements, current proposal, source information and project conditions. A report’s technical relevance and a separate servicing-allocation deadline are different questions.
Can an addendum confirm that municipal capacity is reserved?
Do not treat a report update as an allocation decision. Engineering assessment and municipal servicing-allocation status serve different purposes. Obtain the applicable authority records and keep administrative conditions separate from technical findings.
What if the original report is incomplete?
Request the missing report sections, appendices and referenced submissions. Tell the engineer what remains unavailable. The appropriate scope may change if the baseline cannot be established; do not describe an incomplete record as a verified foundation for an update.
Should the old report be deleted after a revised issue?
Preserve the project record while clearly identifying the current submission. Avoid leaving obsolete files indistinguishable from current ones in the working package. The aim is traceability, not erasing the history of the assessment.
How long does an FSR update take?
Timing depends on the work, available inputs, coordination and review requirements. Establish the scope before requesting a programme. A short document can require substantial assessment, while a longer consolidated report may retain clearly identified suitable material.
What is the next step if the reviewer’s instruction is unclear?
Have the project team obtain clarification through the established review channel. Record the question, response and affected submission requirement. Continue independent information gathering, but do not interpret silence as acceptance of a proposed addendum.
Geographic Locations That We Service:
Our Licensed Professional Engineers provide engineering and design consulting for Ontario projects. Related work can include site grading plans and erosion and sediment control plans where required by the agreed project scope.
We provide engineering services across a wide range of municipalities, each with its own requirements and review processes.
Toronto and Surrounding Areas
We provide engineering services in Toronto and provide grading engineering resources through our Toronto grading plan page.
Our service area also includes Oshawa, Pickering with our Pickering grading plan resources, and Clarington.
We also provide engineering services in Ajax through our Ajax grading plan resources, Whitby, Brock, Scugog, and Uxbridge, including our Uxbridge grading plan resources.
Halton Region
Within Halton Region, we provide engineering services in Burlington, including projects requiring Burlington grading plans.
We also provide engineering services in Halton Hills, supported by our Halton Hills grading plan resources.
Our service area also includes Milton and Oakville, including our Oakville grading plan resources.
Peel Region
Within Peel Region, we provide engineering services in Brampton, including projects requiring Brampton grading plans.
We also provide engineering services in Mississauga through our Mississauga grading plan resources and Caledon through our Caledon grading plan resources.
York Region
Within York Region, we provide engineering services in Vaughan and provide information about Vaughan grading plans.
We also provide engineering services in Aurora through our Aurora grading plan resources and East Gwillimbury through our East Gwillimbury grading plan resources.
Additional service areas include Georgina with our Georgina grading plan resources, Markham with our Markham grading plan resources, and Newmarket with our Newmarket grading plan resources.
We also provide engineering services in Richmond Hill with our Richmond Hill grading plan resources, Whitchurch-Stouffville through our Whitchurch-Stouffville grading plan resources, and King through our King grading plan resources.
Our service area also includes Bradford West Gwillimbury.
Other Southern Ontario Cities and Towns
We provide engineering services in many additional Southern Ontario communities, including Hamilton, St. Catharines, Niagara-on-the-Lake, Brant, Cambridge, Kitchener, Waterloo, and Woodstock.
We also provide engineering services in Guelph, Centre Wellington, Shelburne, Orangeville, New Tecumseth, Essa, Collingwood, Wasaga Beach, and Barrie, including our Barrie grading plan resources.
Additional service areas include Midland, Orillia with our Orillia grading plan resources, Ramara, Minden Hills, North Kawartha, Kawartha Lakes, Peterborough, Selwyn, and Brighton.
