The executive director sat across from the board chair in the small conference room adjacent to the agency's administrative offices, a thick folder resting on the table between them. The folder contained what documentation existed from the renovation project completed four years earlier: the construction contract, some photographs taken during the work, a handful of inspection reports, and correspondence with the general contractor that grew increasingly sparse as the project neared completion. What the folder did not contain was equally significant. There was no systematic record of decisions made during construction, no documentation of the verbal assurances given when certain foundation issues arose mid-project, and most critically from the perspective of this particular meeting, no clear articulation of what the government funder expected in return for its substantial capital contribution. The water infiltration problem that had forced the temporary relocation of two vulnerable-population programs had also triggered questions from the funder's regional office, questions the executive director found difficult to answer because the agency had never clearly understood what answering to the funder actually required. The board chair listened as the executive director explained that pursuing the general contractor would not be a simple matter of filing a claim and waiting for resolution. The funder had contributed nearly forty percent of the renovation budget. That contribution, the executive director had recently learned, came with strings that extended well beyond the completion certificate.
The relationship between a capital funder and the organization receiving that funding is fundamentally different from an ordinary grant for programming or operations. When a government funder contributes money toward a capital project, the funder acquires an interest in the physical asset that is being created or improved. This interest may be explicit, expressed through clauses in the funding agreement that restrict how the asset can be used, disposed of, or encumbered for a specified period. The interest may also be implicit, arising from the funder's mandate to ensure that public money achieves lasting public benefit. Either way, the funding relationship creates ongoing obligations that persist long after the construction crews have departed and the final invoice has been paid. These obligations are not merely administrative inconveniences; they represent genuine exposure for the recipient organization, exposure that becomes acute when something goes wrong with the project and the organization must decide how to respond.
The funding agreement that governed the capital contribution to this agency's renovation was a standard form document, one that the government funder used across dozens of similar projects throughout the province. The agency's executive director at the time of the project, who has since retired, signed the agreement without significant negotiation. The board approved the acceptance of the funding at a regular meeting, the minutes of which record only that the board "accepted the capital grant as presented" with no discussion of the terms or their implications. This pattern is common among non-profit organizations receiving government funding for capital projects. The organization is grateful for the money, eager to proceed with the work, and reluctant to appear difficult or ungrateful by questioning the terms of what is, after all, a gift of public funds for a worthy purpose. The consequence of this approach is that organizations frequently do not understand what they have agreed to until circumstances force them to examine the agreement closely, often at a moment when the stakes have become significant.
A capital funding agreement typically imposes several categories of obligation on the recipient organization. The first category concerns the use of the funds themselves: requirements that the money be spent only on eligible costs, that expenses be documented according to specified standards, that the funder be notified of changes to the project scope or budget, and that the organization provide financial reporting demonstrating how the funds were actually deployed. The second category concerns the asset created or improved with the funding: restrictions on disposing of the asset, requirements to maintain the asset in good condition, prohibitions on using the asset for purposes inconsistent with the funder's objectives, and often a provision giving the funder the right to recapture some or all of the contribution if these conditions are violated. The third category concerns accountability and transparency: requirements to acknowledge the funder's contribution publicly, to permit inspections or audits, to report on outcomes achieved through the funded project, and to notify the funder of circumstances that might affect the project or the asset.
The third category is where organizations most frequently encounter unexpected exposure when construction deficiencies emerge. A funding agreement may require the organization to notify the funder of any "material change" affecting the project or the funded asset. Water infiltration causing structural damage and forcing the relocation of programs is unquestionably a material change. Yet many organizations, when confronted with such problems, do not immediately think to contact the funder. They focus on the immediate operational crisis, on the disruption to their clients and programs, on the relationship with the contractor who they believe is responsible. The funder exists in their minds as the source of the money, not as an ongoing stakeholder with legitimate interests in the outcome. This misunderstanding can have serious consequences. A funder that learns of significant problems through channels other than the recipient organization may reasonably question whether the organization can be trusted to manage the asset responsibly. That question may affect not only the current project but future funding relationships as well.
The agency in this scenario did not notify its government funder when the first signs of water infiltration appeared approximately two years after the renovation was completed. The executive director at the time believed the problem was minor, something that could be addressed through routine maintenance. When the problem recurred and worsened, the organization was preoccupied with finding alternative space for the affected programs and did not think to update the funder. It was only when the current executive director, newly appointed to the role, conducted a thorough review of the organization's files and discovered the funding agreement's notification requirements that the funder was formally advised of the situation. By that point, the funder's regional office had already heard about the program relocations through community channels. The first formal communication from the organization arrived after the funder had already begun asking questions internally about what had happened to the project it had supported.
This sequence of events illustrates a principle that applies broadly to funder relationships in the context of capital projects: the organization receiving funding must understand itself as being in an ongoing relationship with the funder, not simply as the recipient of a one-time transaction. The funding agreement is not merely a set of conditions that must be satisfied to receive the money; it is the charter governing a relationship that continues for the duration of the asset's useful life, or for whatever period the agreement specifies. Managing that relationship requires the same attention to communication, documentation, and mutual understanding that the organization would bring to any other significant relationship, whether with a major donor, a key partner agency, or an important vendor.
When a construction deficiency dispute arises in the context of a funded capital project, the funder relationship creates several specific areas of exposure that the organization must manage carefully. The first concerns the potential for clawback of the capital contribution. Most funding agreements include provisions allowing the funder to demand repayment of some or all of the contribution if certain conditions are not met. These conditions typically include maintaining the asset in good condition and using it for the purposes contemplated in the funding application. If an organization allows a building to deteriorate to the point where it can no longer serve its intended purpose, the funder may have grounds to demand repayment. The fact that the deterioration resulted from a contractor's deficient work rather than the organization's own neglect may or may not be a defence, depending on how the funding agreement is drafted and how the funder chooses to interpret it. An organization facing a demand for repayment of a substantial capital contribution while simultaneously dealing with the cost of repairing construction deficiencies faces a financial crisis that may threaten its continued existence.
The second area of exposure concerns the potential conflict between the organization's interests and the funder's interests in managing the deficiency dispute. The organization's primary interest is typically to obtain full compensation for its losses, whether through negotiation with the contractor, litigation, or some combination of both. The funder's interests may be more complex. A government funder may have relationships with the contractor that it wishes to preserve. The funder may have concerns about the publicity that litigation could generate, particularly if the litigation reveals that the funder's own oversight of the project was inadequate. The funder may prefer a quiet resolution that minimizes public attention, even if that resolution does not fully compensate the organization for its losses. When the funder contributed forty percent of the project cost, as in this scenario, the funder's preferences carry significant weight. An organization that proceeds with litigation over the funder's objections may find that its future funding applications receive less favorable treatment, a consequence that is rarely stated explicitly but is nonetheless real.
The third area of exposure concerns the documentation demands that a funder may make once a deficiency dispute has arisen. A funder learning that a project it supported has developed serious problems will typically want to understand what happened and why. This may prompt requests for copies of all project documentation, all correspondence with the contractor, all inspection reports, and all internal communications regarding the project. If the organization's documentation is incomplete, as is the case for the agency in this scenario, the process of responding to funder requests will reveal the gaps. Those gaps may raise questions about the organization's competence and diligence, questions that affect the funder's confidence in the organization's ability to manage the deficiency dispute effectively. In extreme cases, a funder may conclude that the organization's poor project management contributed to the problems that emerged and may seek to hold the organization partly responsible.
The limitation period question that the board must consider in this scenario is complicated not only by the difficulty of determining when someone first knew something was wrong, but also by the potential need to coordinate the organization's legal strategy with the funder's interests. If the organization concludes that a limitation period is about to expire and files a claim to preserve its rights, it is taking an action that affects the funder's interests. The funder may have views about whether litigation is appropriate, which claims should be advanced, which parties should be named, and how the matter should be conducted. Proceeding without consulting the funder may be necessary to protect the organization's legal rights if time is short, but it may also damage the funder relationship in ways that create longer-term costs. A board facing this situation must weigh the immediate legal risk of missing a limitation period against the relationship risk of acting without the funder's knowledge or consent.
The documentation practices that should have been in place from the beginning of this project would have served multiple purposes. First, contemporaneous records of decisions, inspections, and contractor communications would provide the evidentiary foundation for any claim against the contractor. Second, those same records would demonstrate to the funder that the organization managed the project competently and is therefore entitled to the funder's support in pursuing remedies. Third, systematic documentation of the funder relationship itself, including records of what the organization understood its obligations to be and how it sought to fulfill them, would provide protection against any suggestion that the organization failed to meet its commitments under the funding agreement. The absence of this documentation leaves the organization exposed on all three fronts. It has weaker evidence for its claim against the contractor, less credibility with the funder, and limited ability to defend itself if the funder questions whether it met its obligations.
The board's deliberations about whether to pursue the contractor must therefore include explicit consideration of the funder relationship and how that relationship will be managed as the dispute proceeds. The board should begin by ensuring that it has a complete and accurate understanding of the funding agreement's terms. This may require legal review, as funding agreements are often dense documents with provisions that interact in complex ways. The board should understand what notification obligations the agreement imposes, whether those obligations have been satisfied, and what the consequences might be if they have not. The board should understand what the agreement says about maintaining the asset and whether the organization's handling of the deficiency issue could be characterized as a failure to maintain. The board should understand whether the agreement contains any provisions that might be relevant to litigation, such as requirements to obtain the funder's consent before taking legal action that could affect the funded asset or provisions addressing how any recovery obtained through litigation would be shared between the organization and the funder.
Once the board understands the contractual framework, it must develop a strategy for engaging with the funder. The starting point should be honest acknowledgment of the situation, including any failures of communication that have occurred. A funder learning of problems through community channels rather than through the organization will already have concerns about the organization's transparency. Attempting to minimize or explain away the communication failures will likely deepen those concerns. A more effective approach is to acknowledge the failures, explain what circumstances led to them, describe what the organization has learned, and outline what steps the organization intends to take going forward. This approach treats the funder as a partner with a legitimate interest in the outcome, which is what the funding relationship actually makes them.
The engagement with the funder should include a clear request for the funder's views on how the deficiency dispute should be managed. The funder may have preferences about whether to pursue negotiation or litigation, which parties to involve, and what outcomes to seek. The organization is not obligated to follow the funder's preferences in every respect; it remains an independent organization with its own interests and its own fiduciary obligations. However, understanding the funder's perspective allows the organization to make informed decisions about when to align with the funder's preferences and when to diverge. It also creates a record that the organization sought the funder's input, which may be important if the funder later questions the organization's handling of the matter.
The question of whether and how any recovery from the contractor should be shared with the funder is one that organizations often fail to consider until they have already reached a settlement or obtained a judgment. The funding agreement may address this question explicitly, requiring that recoveries be applied to repair the funded asset or returned to the funder in proportion to its contribution. Even if the agreement is silent, the funder may have expectations about how a recovery should be used. An organization that settles a construction deficiency claim and uses the settlement funds for purposes unrelated to the funded asset may find that the funder regards this as a violation of the funding relationship's implicit terms. The board should determine the funder's position on this question before any settlement negotiations are seriously underway.
The contractor's defence that a subcontractor is responsible for the foundation problems that led to the water infiltration introduces additional complexity into the funder relationship. From the organization's perspective, the general contractor is responsible for the work of its subcontractors, and the internal allocation of fault between them is not the organization's concern. From the funder's perspective, however, the involvement of a subcontractor may be relevant. If the subcontractor is also a contractor that the funder works with frequently, the funder may have interests in how the dispute is framed and resolved that differ from the organization's interests. If the subcontractor was selected or approved by someone other than the organization, such as a government project manager who oversaw the funded work, the question of responsibility may implicate the funder's own processes. These considerations may not change the organization's legal strategy, but they should inform the organization's communication with the funder about what the litigation is likely to involve.
Throughout the process of managing the funder relationship in the context of a deficiency dispute, the organization must maintain thorough documentation of all communications and decisions. This documentation serves the same purposes that project documentation should have served during construction: it provides evidence of what occurred, it demonstrates the organization's diligence and competence, and it protects the organization against later claims that it failed to fulfill its obligations. Every communication with the funder should be documented in writing, either through written correspondence or through a contemporaneous memo to file summarizing verbal conversations. Every decision about how to proceed should be recorded in board minutes or executive director reports, with clear articulation of the factors considered and the reasons for the decision reached. If the funder provides guidance or expresses preferences, those should be documented precisely, along with the organization's response.
The experience of this agency illustrates what can go wrong when an organization receives capital funding without fully understanding the relationship it is entering. The funding agreement was signed without careful review of its terms. The ongoing obligations it created were not integrated into the organization's operational practices. When problems emerged with the funded project, the funder was not notified in accordance with the agreement's requirements. When the organization finally engaged with the funder, it did so from a position of weakness, having already demonstrated that it did not understand or prioritize the funder relationship. The board now faces not only the challenge of pursuing the contractor for the construction deficiencies, but also the challenge of repairing a funder relationship that has been damaged by years of inattention.
For other organizations embarking on capital projects with government funding, this scenario offers clear lessons about what should be documented and when. Before accepting capital funding, the organization should ensure that it understands all of the obligations the funding agreement creates, not just at the time of the grant but throughout the life of the asset. During the project, the organization should maintain documentation sufficient to demonstrate compliance with all funding requirements and to provide evidence of how the project was managed. After the project is complete, the organization should establish systems to ensure ongoing compliance with asset maintenance and reporting requirements, and it should maintain awareness of notification obligations that might be triggered by future events. When problems emerge, the organization should communicate promptly and transparently with the funder, treating the funder as a partner with legitimate interests rather than as a bureaucratic nuisance to be managed. These practices do not guarantee that disputes will be avoided or easily resolved, but they position the organization to manage disputes effectively when they arise, protecting both its immediate interests and its long-term relationship with the funders whose support enables its mission.