1. The municipal decision behind the grant
A funding program asks whether a project is eligible and competitive. A municipality has a different decision to make: whether pursuing and accepting the funding advances its own priorities on acceptable terms. Those questions may lead to the same answer, but they are not interchangeable.
The practical starting point is: What would the municipality most plausibly do without the grant? The answer identifies what the opportunity may change, what commitment would remain with the municipality and what alternatives may be set aside. Concluding that a project would not proceed without the grant does not make it a poor project or automatically support rejection. That may be precisely the public purpose of the funding. The answer instead allows staff, senior management or Council, or whoever holds delegated authority, to consider that change consciously.
I reviewed 12 Ontario municipal transportation projects and the grant decisions attached to them. I used public municipal documents: Council and staff reports, capital budgets, asset management plans, tender awards and later progress reporting.
Those documents were consistently clear about three things: why a project was wanted, whether it was ready to build, and where the capital was coming from. They were much less clear about four others: what the municipality would have done without the grant, what else the money and staff time could have gone to, what the project would cost to own over its life, and what it actually delivered once built.
That finding describes what municipalities published. It does not describe what they thought. A report that does not discuss an alternative is not evidence that staff ignored it. Nothing in the 12 cases suggests grants pulled municipalities away from their own priorities. I chose the 12 projects because their records were unusually complete, so they show what is possible to trace. They do not show what is typical across Ontario.1
2. How the 12 cases were reviewed
Understanding the findings in the next section means knowing how I examined each project and what the labels mean. This section sets out both. The technical companion carries the full method in its Sections 2 and 3.
I traced each project through three points in time: what the municipality had decided before the funding opportunity appeared, what it decided when the funding was on the table, and what it reported afterwards. I used only public documents. Where a document did not address a question, I recorded an unanswered question. I never read a silent document as a negative answer.
I then sorted the 12 projects using a fixed set of labels, applied consistently and reviewed case by case. Capitalized terms in this section and Section 3 are those labels, summarized below. Sections 4 to 8 use Investigate, Apply and Accept as the names of the three proposed decisions. Those three are guidance stage names. They are not case labels.
Table 1: The labels used in this paper
| Labels | What they describe | What they mean |
|---|---|---|
| Established Priority; Identified Future Need | Where the project stood before the grant | An Established Priority was already approved and programmed. An Identified Future Need appeared in an approved plan but had no funding yet. |
| Helpful; Material; Explicitly Contingent | How much the project relied on the grant | Helpful means the money assisted. Material means it was a significant part of the financing. Explicitly Contingent means the municipality stated in writing that the project would not proceed without it. |
| Additional; Indeterminate | What the grant can be shown to have changed | Additional means the record shows the work probably would not have gone ahead without the funding, within the period the documents cover. Indeterminate means the public record simply does not answer the question, which is not the same as finding the grant changed nothing. |
| Reinforcing; Adaptive | How the grant sat alongside municipal plans | Reinforcing means the funding supported an existing need and its delivery or affordability. Adaptive means scope, timing, financing or operations shifted while the underlying purpose held. Neither is a criticism. |
| Potentially Distortionary; Distortionary | Whether the grant pulled a municipality off course | Reserved for cases where funding drew a municipality toward work it had not identified as a priority, at a cost to something it had. No case in this study met either threshold. |
| Complete; Partial; Limited; Not Found; Not Applicable | How much the documents actually said | Describes the public evidence available on a question. Not Found means the review did not locate it in the documents reviewed, not that the municipality failed to consider it. Not Applicable means the question did not arise for that case. |
Three funding types appear in the study. Competitive grants require an application and are awarded against other applicants, so the municipality cannot count on the money. Matching capital contributions require the municipality to put up a share of the cost. Predictable transfers, such as the Canada Community-Building Fund, arrive on a known formula and schedule, so a municipality can plan around them years ahead. Six of the 12 projects were competitive, three were matching contributions and three were predictable transfers.
3. What the 12 projects showed
The 12 projects span roads, bridges, trails and electric vehicle charging. They were chosen because their public records were complete enough to follow a project from before the grant to after construction, which makes them useful for detailed comparison and unsuitable as a statistical sample of Ontario.
All 12 addressed either an Established Priority or an Identified Future Need. Seven were already approved and programmed before the funding opportunity appeared; five sat in an approved plan without funding. Eight were Reinforcing and four Adaptive.1
Table 2: What the public records established and where they were less complete
| Decision subject | Public-record picture | Result in the 12 selected cases | Essential qualification |
|---|---|---|---|
| Public policy purpose | Generally established | Complete in 12/12 | Documentation of purpose does not establish achieved benefit. |
| Pre-grant status and readiness | Generally established | 7 Established Priorities and 5 Identified Future Needs; readiness Complete in 11 and Partial in 1 | Readiness is not relative priority and does not establish displacement. |
| Direct capital financing | Generally established | Exact total project cost in 9/12; exact nominal grant amount in 11/12; exact grant share on a valid basis in 7/12 | Shares from different cases cannot be averaged, and no exact grant share is available for the electric vehicle cases. |
| No-grant scenario | Less consistently visible | Complete in 1, Partial in 1, Limited in 1, Not Found in 7 and Not Applicable in 2 | Not Found is a bounded public-record result, not proof of absent internal consideration. |
| Opportunity cost | Less consistently visible | Complete in 0, Partial in 6, Limited in 5 and Not Found in 1 | The finding does not establish inadequate internal analysis. |
| Lifecycle and operating responsibilities | Less consistently visible | Complete in 4, Partial in 6, Limited in 1 and Not Found in 1 | Complete does not necessarily mean a quantified affordability model. |
| Actual use and performance | Difficult to assess after implementation | Actual use Complete in 2, Partial in 1 and Not Found in 9; performance reporting Complete in 2 and Partial in 10 | Measures differed, and missing use data is not evidence of non-use or failure. |
| Post-approval adaptation | Difficult to interpret after implementation | Complete in 8 and Partial in 4 | Most observed adaptation concerned implementation; improved outcomes were not established. |
Source note: 1. Counts describe the selected 12-case sample only.
A useful distinction emerged here, and it is the heart of the study. Municipal reports consistently showed where the money came from, and much less often showed what difference the money made. Those are different questions, and a large grant answers only the first.
Consider what that meant in practice. In 11 of the 12 projects, the public record could not answer whether the work would have gone ahead without the grant, so the effect was recorded as Indeterminate. That is again a statement about what was published. Staff may well have worked the question through internally without reporting it, and a public-record review cannot see that.
Only Oshawa answered it directly: its approved capital project sheet stated that construction would not proceed if the application failed. That single case is the only one where the record supports calling the funding Additional, and it says nothing about the other 11.
What happened after approval was similarly uneven. Projects commonly changed after the award, but the changes were about getting the work built: design refinements, construction sequencing, procurement, financing arrangements, new operating policies. That pattern matters because it shows where municipal attention went after approval. Adjustment was normal and it was competent, and it was directed at delivering the project as approved. It was not directed at asking whether the approved project was still the right one. That is different from a municipality adjusting a project because it measured how the finished asset was performing. Many of these projects were recent, and a trail, a bridge and a charging network cannot be judged on the same timeline, so there was limited ground for assessing results.
Read together, the review of the 12 case studies points to an opportunity for a clearer decision-making framework. It does not show that municipal decision-making was poor, that municipalities failed to weigh lifecycle costs or competing priorities, or that one kind of funding produced better decisions than another. The technical companion carries the full methods, the formal tests, the financial rules and all 12 case profiles.
4. One integrated municipal grant-decision system
What follows is a system I am proposing to help a municipality decide whether a grant opportunity is worth pursuing, and whether to accept an award once it arrives. Everything from here on is professional guidance. None of it is a finding. I developed it after the analysis, drawing on the gaps the 12 cases revealed. I did not apply it to those cases and it has not been tested in practice.
The guidance takes the form of three decisions a municipality faces as a funding opportunity moves through it, which I call Investigate, Apply and Accept:
- Investigate asks whether an opportunity is worth any further staff time.
- Apply asks whether the municipality should submit an application.
- Accept asks, once an award actually arrives, whether the municipality should take it on the terms offered.
These are three separate decisions and not one long approval. That is the point. A municipality that decides to investigate has not decided to apply, and one that applies has not decided to accept.
Two ideas run through all three. The first is the no-grant scenario: what the municipality would most plausibly do if the funding never arrived. Answering it honestly is what shows whether a grant is paying for something already committed or drawing the municipality toward something new. The second is the full municipal commitment, meaning everything the municipality takes on beyond the matching share: ineligible costs, staff time, and the cost of operating, maintaining, renewing and eventually replacing whatever gets built.
Each of the three decisions should also leave a short written record behind it. A Municipal Grant Decision Summary, provided at the end of this paper, is designed to hold that record in one place.
None of this is mandatory, none of it produces a score, and municipalities should adapt it to their own reporting practices. How much work each decision deserves depends on the size of the project, how novel it is, how uncertain the costs are and how much the municipality would be taking on.
Three case illustrations appear in the sections that follow. Each shows documented municipal practice relevant to a stage. None is a complete application of the proposed system.
Table 3: Decision stage and depth of work
| Decision stage | Municipal question | Proportionate analytical depth | Core record or output | Possible outcomes |
|---|---|---|---|---|
| Investigate | Is the opportunity worth investigating? | Light screening | Initial need, project status, no-grant scenario, exposure, constraints and screening rationale | Continue investigating; obtain more information; defer; decline; or escalate |
| Apply | Should the municipality apply? | Preliminary analysis | Formal no-grant scenario, realistic alternatives, preliminary full commitment, risks and application rationale | Authorize an application; revise before applying; defer; decline; or escalate |
| Accept | Should the municipality accept the funding and commit resources? | Final confirmation | Actual award and conditions, confirmed funding and full commitment, final rationale and post-completion review plan | Accept; accept with conditions or further approval; resolve outstanding matters; defer acceptance; decline; or escalate |
These stages build on one another. Work done at Investigate can be carried into Apply, and Apply into Accept, as long as it still holds. When costs, scope, conditions or risks move, staff should revisit the earlier conclusion instead of assuming it still holds. Reviewing the project after completion is a commitment made at Accept, not a fourth decision.
Who signs off will differ from one municipality to the next. Looking into an opportunity may need nothing more than a manager’s direction. Submitting an application may fall to a staff member already authorized to make that call, or may require a senior manager or Council. Accepting an award may need a budget amendment or a fresh Council decision on top of that. This guidance does not change any of those authorities. What it offers is a consistent thread of information, so that the need behind the project, what would happen without the grant, what the municipality is taking on and what remains unresolved stay with the file as it moves.
When deeper review may be warranted
Use professional judgment to involve technical, finance, asset management, senior management or approval authorities when one or more of the following is material:
- the project was not an established municipal priority, or the municipality would not otherwise proceed;
- municipal, ineligible or potentially unfunded costs are material;
- reserves, debt, operating budgets, staff capacity or competing capital projects may be affected;
- utilization, revenue or public benefit assumptions are uncertain;
- a new service or technology creates continuing obligations;
- procurement or construction timelines are compressed;
- ownership, operations, maintenance, renewal or replacement responsibility is unclear;
- the award differs materially from the application; or
- nobody has been named to review how the finished project performs, and no baseline, data source or timing has been set.
These are prompts to look harder, scaled to what is at stake. They are not grounds for automatic rejection, scoring factors or legal tests.
5. Decision 1: Investigate
The first decision is a quick but disciplined screening. Its purpose is to decide whether the opportunity is worth more staff time. It is not a business case.
Start with the need itself, established independently of the funding: is this something the municipality has already said it wants to do? Then establish where the project stood before the opportunity appeared. It may be an idea, a need named in a plan, an approved design, a line in the capital forecast, a project ready to tender, or work already underway.
Next, determine what would happen if a grant were not awarded. Would the municipality carry on as planned, do the work later, scale it back or build it in phases, look for another funding source, or set it aside for now? An early answer, even a rough one, is more useful than none.
Screening should also put rough numbers to what the municipality would be taking on: the expected contribution, any obvious costs the program will not cover, the staff effort involved, schedule pressure, and new operating or maintenance duties. Check that the project is eligible, that the municipality has the capacity to deliver it, and that the program’s application and construction deadlines are realistic. Keep a short written note of why the opportunity is worth pursuing, or why it is not, and carry any unanswered questions forward.
This stage is also the right time to identify who needs to be involved next. A routine asset-renewal opportunity may stay within the responsible service area until cost and eligibility are confirmed. A project that could draw on reserves, add a new service, require unusual procurement or create a long-term operating obligation may warrant early input from finance, procurement, operations or asset management. Early coordination should match the exposure; it need not become a full interdepartmental review for every intake.
Fort Erie illustration
What the case illustrates: Fort Erie’s Ott Road Bridge was an Established Priority, meaning the Town had already approved and programmed the work. A bridge condition assessment had flagged the structure as needing replacement within one to five years, and by the time the financing was settled the design, environmental review and tendering were all complete. The Town’s capital report set out CAD 1,565,000 in available funds: CAD 1,126,250 from the Canada Community-Building Fund and CAD 438,750 from the Bridge & Culvert Reserve. A municipality that arrives at a funding decision with the need documented, the project ready to build and the money identified has done most of the Investigate work already.
What the record does not establish: The funding here was a predictable transfer the Town could plan around, so the record cannot show that the money caused the project or set its timing. It is also worth separating two things the record shows: this bridge was ready to build, which is not the same as it being Fort Erie’s most urgent need. Readiness tells you a project can proceed, not that it should come first.
Source note: 2.
6. Decision 2: Apply
An open intake does not by itself justify an application. Before seeking authority to apply, staff should work out what the municipality would do without the grant, and then explain why applying is the better course.
Determining how a project would be funded without a grant matters because each option carries a different consequence. Waiting may cost more later, or leave an aging asset in service longer than it should be. Building in phases may keep the work affordable but deliver less of the network benefit. Drawing on reserves or debt may push another project down the list. Even money the municipality already has is money it cannot spend twice.
The application should also record what the municipality will do if the award does not come, or comes smaller or later than hoped. Setting that out in advance keeps the application from quietly becoming a commitment to build regardless of the answer, and it gives whoever considers the eventual award a clear basis for comparison.
This is also the point to analyze the full municipal commitment for the first time, meaning everything the municipality would carry beyond the grant. That includes the municipal share, costs the program will not fund, costs that may end up unfunded altogether, the effect on operations, maintenance and staff, and the eventual bill for rehabilitating or replacing the asset. Consider what all of that does to reserves, borrowing room, the capital program, operating budgets and staff availability. Note the risks around readiness, procurement, schedule, compliance and delivery, including anything that would make applying impractical or make a later award unattractive.
Preliminary analysis should be clear about assumptions. The application may rely on an early cost estimate, an expected funding percentage, anticipated eligibility rules or a delivery schedule that has not been tender-tested. Record the basis, range and owner of each material assumption and state what must be confirmed before acceptance. This creates a practical comparison point when the award arrives and helps prevent an outdated application estimate from being treated as the final municipal commitment.
Keep two things separate in the rationale: the need the municipality has, and the particular project being put forward to meet it with this grant. They are not the same, and a funding program’s eligibility rules can quietly reshape the second. Being explicit about both makes it easier to tell later whether an award still serves the original need.
Council or a delegated authority may attach conditions when authorizing an application, such as a ceiling on the municipal contribution, a limit on what the project will include, or a requirement to review the funding agreement before signing. Carry those conditions forward in writing, because they are what the acceptance decision will be measured against.
Oshawa illustration
What the case illustrates: Oshawa’s Harmony Creek Trail Link 3 was an Established Priority. The trail appeared in the City’s plans well before the funding opportunity, and the design had already been funded. What makes this case unusual is that the City wrote down its no-grant scenario. Its approved capital project sheet stated plainly that construction would not proceed if the Active Transportation Fund application were unsuccessful, and would instead wait for a future Council approval. Against the approved project cost of CAD 2.5 million, the federal contribution was CAD 1.5 million and the City’s CAD 1 million.
This statement is why this is the only project in the study where the grant’s effect could be established. It is the sole Explicitly Contingent case, meaning the municipality itself stated the project depended on the funding, and the sole Additional one, meaning the record supports concluding the construction would not have gone ahead when it did without the grant.
What the record does not establish: The grant did not create the need or the design; both predated it. And because only one municipality in 12 wrote its no-grant scenario down, this result says nothing about the other 11, where the same may or may not have been true. What later happened to cost, scope or schedule on this project cannot be laid at the grant’s door either.
Source note: 3. An adjacent trail link, Coldstream–Delpark, was funded separately and is not part of this case.
7. Decision 3: Accept
An award should be treated as new information, not as an instruction to proceed. By the time it arrives, months may have passed, costs may have moved and the terms may not match what was applied for. Accepting should therefore be a fresh decision, made on the actual amount offered, the final conditions attached to it, and the best current picture of scope, cost, risk and public benefit.
Staff should begin by bringing the project file up to date. This means confirming the current scope and cost, what the award actually is, which costs the funder will count as eligible, what conditions come with the money, and what has changed since the application went in. Staff should then look again at what the municipality would do without the grant. If the award is smaller, later or more restrictive than expected, the reasoning that supported applying may no longer hold.
Staff should then confirm the full municipal commitment, covering:
- municipal funding sources, and all municipal, ineligible, contingency, escalation and potentially unfunded costs;
- effects on the capital budget and forecast, reserves, debt, competing projects, operations and staff capacity; and
- procurement, schedule, compliance, implementation and overrun risks.
Where costs, demand, revenue or technology are uncertain, staff should use reasonable ranges or an adverse scenario instead of a single figure.
Staff should identify what has changed since the application was submitted and set it out plainly, even where the underlying need is as sound as ever. Any of the following can alter the recommendation, and sometimes alter who has authority to approve it:
- a lower award than applied for;
- a changed rule about which costs are eligible;
- extra scope the municipality has to absorb;
- a tighter completion deadline; or
- a revised cost estimate.
The report should then state whether the original reasoning still holds, whether conditions can manage what has changed, or whether staff should revise the project, defer it, decline the award or go back for further approval. Where the funding agreement imposes real obligations, such as procurement rules, reporting duties, completion deadlines, repayment exposure or restrictions on how the asset is used, name the person or unit responsible for each.
Municipal commitment extends beyond initial capital to:
- operations and routine maintenance;
- administration and staffing;
- utilities and technology;
- rehabilitation and component replacement; and
- renewal and eventual decommissioning where applicable.
Realistic revenue, recoveries and avoided costs belong in the analysis, but financial performance is not the sole measure of public value. Safety, accessibility, environmental, equity, service and economic-development objectives may justify an ongoing municipal subsidy when the commitment is understood and consciously approved. Table 4 gives examples of that continuing exposure for the asset types in this study, with questions worth asking at acceptance.
Table 4: Concise lifecycle considerations by asset type
| Asset type | Continuing municipal exposure | Useful acceptance-stage questions |
|---|---|---|
| Roads and bridges | Inspections, winter service, drainage, pavement or structural maintenance, rehabilitation, traffic management and eventual renewal | Are condition, safety, detour and renewal obligations reflected in the capital and asset management sequence? Which construction or deterioration scenarios require attention? |
| Active transportation facilities | Surface and drainage maintenance, vegetation, winter service where intended, lighting or structures, accessibility, rehabilitation and user information | Who owns maintenance and accessibility standards? What baseline, use, connectivity or safety information is practical to collect? |
| Electric vehicle charging infrastructure | Electricity and demand charges, networking, maintenance, customer support, pricing or subsidy, technology obsolescence, component replacement, renewal and decommissioning | Who monitors availability, sessions, energy, cost and revenue? How will pricing, accepted subsidy, contracts, replacement and technological change be reviewed? |
If a municipality accepts the grant, it should also settle what the project is meant to achieve and how anyone will later know whether it did. A monitoring plan does not have to be elaborate. It should name:
- the measure;
- a starting point to compare against, where one is available;
- where the data will come from;
- who will collect it, and which unit is answerable for it;
- when the review happens; and
- who receives it.
That later review is where the municipality learns something it can use next time. It can cover:
- what the project finally cost, and what the municipality ultimately contributed;
- whether the scope changed materially;
- how the asset has been to operate, how much it is used and what it appears to be delivering;
- where the significant variances came from;
- what renewal will eventually demand; and
- what any of that suggests for the next funding decision.
This is follow-through on Decision 3, not a separate stage.
Dufferin illustration
What the case illustrates: Dufferin’s county-wide charging network was an Identified Future Need. The County’s Dufferin Climate Action Plan set out the demand rationale, and its Electric Vehicle Charging Station Policy 5-6-09 assigned responsibility for energy costs, maintenance, replacement, data and fee review. Later reporting included charging sessions, connection hours, energy and an emissions measure, together with continuing fee and network review.
What the record does not establish: The financial figures are lower bounds: total cost above CAD 627,000, federal funding above CAD 289,000 and County funding above CAD 338,000. They do not support an exact grant share, and the record does not establish achieved cost recovery or improved outcomes.
Source note: 4.
8. Recording the municipal decision
Whatever route a decision takes, whether a manager’s approval, a delegated authority, a budget amendment or a full Council report, the written record can cover the same points. The test is whether someone picking it up later can see what the municipality chose, why, and where the supporting work sits.
At whichever stage applies, a municipality should be able to set out:
- the need the project addresses, and where it stood before the funding appeared;
- what the municipality would do without the grant, and what the realistic alternatives are;
- what the project costs, split into the grant, the municipal share, costs the program will not cover and costs that may end up unfunded;
- what the municipality takes on for the life of the asset;
- what else the money and staff time could have gone to;
- the funding conditions and delivery risks that matter;
- what the project is expected to achieve, and how that will be checked afterwards;
- where the supporting reports and analysis can be found; and
- the recommended decision, any conditions attached to it, and the reasoning behind it.
The Municipal Grant Decision Summary at the end of this paper is designed to be that summary, or a cover sheet for a longer report. Fill in only the stage the municipality is actually at, and point to the supporting work instead of reproducing it: the staff report, the business case, the lifecycle costing, the review of the funding agreement, the risk assessment, whatever the project warrants. Where the assessment flags that expanded analysis is appropriate, that is a prompt to go and get it.
Carrying the thread between stages matters as much as filling in any one of them. At Apply, point back to what the investigation found and note which assumptions are being carried forward. At Accept, identify who authorized the application and explain what has changed since in the award, cost, scope, schedule, conditions or risk. Where a condition is attached, say what it requires, who is responsible and whose approval is still needed. Someone reading the file afterwards can then follow how the municipality’s judgment developed as it learned more.
An optional Municipal Grant Award Acceptance and Accountability Worksheet follows the assessment as the second detachable page. It supports Decision 3 where a fuller record is warranted, and that page sets out when it applies and how the two tools work together.
These are suggestions, not requirements, and they produce no score. They are meant to give municipalities a sound and consistent way of deciding whether to pursue a grant, and whether to accept one when it is offered.
9. Conclusion: What the records showed and what to do about it
Across the 12 projects, municipalities typically justified a grant application by linking it to municipal purpose, readiness and direct financing. That was more straightforward than working out what would have happened without the grant, what else the money might have done, what the asset would cost to own, and what it eventually delivered. Those questions were answered less often.
That gap is not evidence of poor decisions. It reflects what municipalities publish, and public reports are not a transcript of internal thinking.
The Investigate–Apply–Accept guidance I am proposing offers a practical discipline and produces no score. It puts the no-grant question at the centre, assesses the full municipal commitment, and writes down the reasoning while it still matters. Municipalities should adapt it to their own authority, risk and practice.
The Municipal Grant Decision Summary at the end of this paper is the main summary of a decision. The optional worksheet that follows it supports the acceptance stage where more detail is warranted. The technical companion holds the methods, the complete findings, the case profiles and the routes to every source.
Author note
I am the author of this paper and prepared it in my own professional capacity. My professional perspective is grounded in municipal transportation planning, engineering and project management. It is not an endorsed position of any organization.
The views in this paper are my own. They are not the views of my employer. No employer commissioned, reviewed, sponsored or endorsed the research or the guidance set out here.
Source notes and companion reference
This paper uses a deliberately light citation layer: aggregate claims and the three case illustrations route first to the technical companion, which supplies the complete analytical trail and readable public-source notes. General professional guidance is not cited as an empirical finding.
All empirical counts, case classifications and case illustrations are drawn from the Technical Companion. Its Table 11 and Schedule F1 show where each statement in this paper draws its evidence; Appendices A–D provide the case profiles, evidence completeness schedules, financial bases and proposition tests; and its numbered notes provide the public-source routes.
Availability of the technical companion. The Technical Companion is a separate document, and it is available on request by email. The notes below route aggregate claims and the three case illustrations to it by section, table, box and schedule, so a reader who wants the full evidence trail behind a number or a case can ask for it. Notes 2 to 4 also name the underlying municipal reports with their dates, and those can be obtained from the issuing municipality independently.
The proposed municipal decision system, detachable assessment and optional worksheet are subsequent professional guidance and should not be attributed to the cases as empirically tested interventions.
Municipal Grant Decision Summary
Complete only the current decision. Scale detail to project scale, uncertainty, novelty and municipal exposure. Summarize judgment here, cite supporting analysis and revisit earlier conclusions when material facts change.
Basic information
| Field | Response | Field | Response |
|---|---|---|---|
| Grant program and intake | Project or initiative | ||
| Responsible department / lead | Decision | ☐ 1 Investigate ☐ 2 Apply ☐ 3 Accept | |
| Approval authority / delegate | Decision date or deadline | ||
| Pre-opportunity project status | Source establishing need / priority | ||
| Total project cost | $ | Grant requested / awarded | $ |
| Municipal cost | $ | Ineligible or potentially unfunded cost | $ |
| Staff report / supporting record | Expanded analysis located in |
Expanded analysis check
This check identifies decisions that need more analysis than this summary can hold. A checked box is not a mark against the project. It indicates where supporting work should be prepared and referenced.
Check any factor requiring expanded analysis outside this summary:
| Financial and delivery | Service and priority |
|---|---|
| ☐ Material municipal cost, financing or budget effect | ☐ New or expanded asset or service |
| ☐ Material capital, operating or staff opportunity cost | ☐ Ongoing operations, maintenance, renewal, replacement, technology or service |
| ☐ Significant funding, procurement, schedule, delivery or compliance risk | ☐ Novel approach or limited municipal experience |
| ☐ Uncertain cost, demand, public value, revenue, recovery or avoided cost | ☐ Effect on competing priorities, reserves, debt, operations or staff capacity |
Expanded analysis: ☐ Not required ☐ Required and referenced above
Decision 1: Is the opportunity worth investigating?
| Minimum investigation record | Response |
|---|---|
| Need or strategic alignment, pre-opportunity status and principal evidence | |
| Initial no-grant course | ☐ Proceed as planned ☐ Later ☐ Reduce ☐ Phase ☐ Other funding ☐ Not in current plan period ☐ Uncertain |
| Preliminary financial / delivery exposure and obvious eligibility, capacity or timing constraints | |
| Why further investigation is or is not warranted |
Decision 2: Should the municipality apply?
| Minimum application record | Response |
|---|---|
| Formal no-grant course and realistic alternatives considered | ☐ Proceed as planned ☐ Later ☐ Reduce ☐ Phase ☐ Other funding ☐ Not in current plan period |
| Consequences of an unsuccessful, reduced or delayed award | |
| Preliminary full commitment: municipal / ineligible costs, financing, lifecycle exposure and capital / operating / staff trade-offs | |
| Known conditions; readiness, procurement, schedule, delivery and compliance risks | |
| Why apply rather than use a realistic alternative |
Decision 3: Should the municipality accept the funding?
| Minimum acceptance record | Response |
|---|---|
| Updated scope and cost | |
| Final award, eligible-cost basis and conditions | |
| What has changed since the application | |
| No-grant course reconfirmed | ☐ Proceed as planned ☐ Later ☐ Reduce ☐ Phase ☐ Other funding ☐ Not in current plan period |
| Full municipal commitment, recorded across the five rows below | |
| Confirmed municipal funding sources | |
| Municipal, ineligible, contingency, escalation and potentially unfunded costs | |
| Operations, maintenance, administration and staffing | |
| Utilities, technology, rehabilitation, replacement, renewal and decommissioning | |
| Realistic revenue, recovery or avoided cost | |
| Uncertainty, adverse cases and effects on competing priorities and resources | |
| Implementation and delivery risks | |
| Expected public outcomes and any accepted subsidy | |
| Measure, baseline, information owner and collection timing | |
| Post-completion review owner and date | |
| What the review will cover: final cost and municipal contribution, scope changes, operations, use and outcomes, variances, renewal implications and lessons |
Recommended decision and rationale
Recommendation: ☐ Proceed ☐ Proceed with conditions ☐ Revise ☐ Defer ☐ Decline ☐ Escalate / further approval
Conditions or next action: ____________________________________________________________________
Concise rationale (address need / alignment, prior status, no-grant course, full commitment, principal risks, expected outcomes and supporting records as relevant):
Decision maker: _______________________________________________ Decision date: ______________
Recommended municipal good practice. Adapt to local delegations, policies and reporting. This summary supports judgment; it is non-mandatory, does not score the decision and does not replace supporting analysis.
Municipal Grant Award Acceptance and Accountability Worksheet
The Municipal Grant Decision Summary is the principal concise decision record or cover sheet. Use this worksheet only as an optional supporting record for Decision 3: Accept when greater documentation is warranted, particularly where:
- the award differs materially from the application;
- municipal, ineligible or potentially unfunded exposure is significant;
- operating, maintenance, staffing, renewal or replacement obligations are new or have changed; or
- the post-completion accountability commitment needs a fuller record.
Municipalities are not expected to complete both tools routinely. When this worksheet is used, summarize the conclusion in the assessment and cross-reference this record; information already documented here need not be entered twice. The worksheet supplements Decision 3 and does not create another process, replace supporting analysis or establish a fourth decision stage.
The worksheet is non-mandatory, non-scored and adaptable to local delegations, budget processes and reporting practices. Complete it proportionately to project scale, uncertainty, novelty and municipal exposure.
Basic information
| Field | Response | Field | Response |
|---|---|---|---|
| Municipality | Department / lead | ||
| Grant program and intake | Project or initiative | ||
| Approval to submit application / date | Award acceptance approval / date | ||
| Funding agreement or award notice | Council, delegated or administrative approval record | ||
| Worksheet owner | Date prepared / updated |
1. Application-to-award change check
Record material changes and explain their decision effect. Use No material change where appropriate instead of leaving a field ambiguous.
| Item | At application | At acceptance / current | Change, reason and decision effect |
|---|---|---|---|
| Funding requested / funding awarded | $ | $ | |
| Total project cost | $ | $ | |
| Eligible-cost basis | |||
| Municipal contribution | $ | $ | |
| Ineligible costs | $ | $ | |
| Potentially unfunded costs | $ | $ | |
| Contingency and escalation allowance | $ | $ | |
| Project scope and principal quantities | |||
| Schedule and completion deadline | |||
| Procurement and delivery assumptions | |||
| Funding conditions and reporting obligations | |||
| Asset ownership and operating responsibility | |||
| Operations, maintenance and staffing obligations | |||
| Asset renewal, replacement or decommissioning obligations |
Updated no-grant scenario:
☐ Proceed as planned ☐ Proceed later ☐ Reduce scope ☐ Phase delivery ☐ Use other funding ☐ Not in current capital-planning period ☐ Other / uncertain
Explanation and realistic alternatives:
Does the original application rationale remain valid?
☐ Yes ☐ Yes, with conditions ☐ Revise rationale / scope ☐ Further review required ☐ No
Basis:
2. Final municipal commitment
| Commitment or exposure | Confirmed position and supporting record | Owner / required action |
|---|---|---|
| Confirmed municipal funding sources, including reserve, debt, tax levy, development charges or other approved source as applicable | ||
| Ineligible, contingency, escalation and potentially unfunded exposure | ||
| Capital-budget or forecast amendment | ||
| Operating-budget and staff-resource effects | ||
| Operations, maintenance, administration, utilities and technology | ||
| Rehabilitation, component replacement, renewal and decommissioning | ||
| Opportunity cost and effects on competing projects or priorities | ||
| Procurement, schedule, compliance and delivery risks | ||
| Material uncertainty and reasonable adverse scenarios | ||
| Expected public value and any consciously accepted ongoing subsidy |
Acceptance recommendation:
☐ Proceed ☐ Proceed with conditions ☐ Revise ☐ Defer ☐ Decline ☐ Escalate / further approval
Conditions, outstanding matters or required Council, delegated or administrative approval:
Concise rationale:
3. Post-completion accountability commitment
Define the smallest useful review that can show whether the asset or service was delivered and is serving its intended municipal purpose. Financial recovery is not the sole measure of public value.
| Accountability field | Acceptance-stage commitment |
|---|---|
| Intended public outcome | |
| Performance measure or indicator | |
| Baseline, where appropriate and available | |
| Data source and collection method | |
| Information owner | |
| Responsible municipal unit | |
| Review timing / target date | |
| Reporting route: management, delegated authority, budget process, Council or other | |
| Expected decision or follow-up from the review | |
| Final cost, municipal contribution and scope information to retain | |
| Operating, maintenance, utilization or outcome information to retain | |
| Renewal implications and lessons for later grant decisions |
Review owner: ____________________________________ Target review date: ____________________
Where the completed review will be retained or reported:
Optional municipal practice aid. Adapt to local processes. Use the Municipal Grant Decision Summary as the concise decision record and cross-reference this worksheet where it provides supporting detail. Do not duplicate information. This worksheet supplements Decision 3, does not score the decision and does not establish a separate post-completion approval gate.
Footnotes
-
Would We Build It Without the Grant? Technical Companion: What 12 Ontario Municipal Cases Show and the Evidence Behind the Findings, Sections 1.2–1.4 and 4.1–4.5, Tables 5–7 and Appendices B–C. Its analytical note records the basis for the counts and classifications. ↩ ↩2 ↩3
-
Technical companion, Box 3 and Schedules A11 and C1. Underlying public sources include Town of Fort Erie, Award of Engineering Services, Replacement of Ott Road Bridge (S051B), Report IS-43-2019 (December 2, 2019); Award of Tender for Ott Road Bridge (S051B) Replacement, Report IS-15-2021 (April 19, 2021); and Bridge & Culvert Repair/Replacement Program (BRIG20) in 2021: Ott Road Bridge Replacement (December 3, 2021). Verified links and locations are in technical-companion source note 15. ↩
-
Technical companion, Box 2 and Schedules A3, C1, D2 and D5. Underlying public sources include City of Oshawa, Active Transportation Fund Update (FIN-22-23) (February 23, 2022) and 2023 Approved Capital Projects (January 19, 2023). Verified links and locations are in technical-companion source note 7. ↩
-
Technical companion, Box 4 and Schedules A8, C1, D7 and D8. Underlying public sources include County of Dufferin, Dufferin Climate Action Plan (March 11, 2021), Electric Vehicle Charging Station Policy 5-6-09 (September 9, 2021) and Charge Up in Dufferin (registered metrics updated December 31, 2025; publication date not established). Verified links and locations are in technical-companion source note 12. ↩