A subcontractor's notice of claim against a performance bond is timely when filed within 90 days of city council ratification, despite being filed over 90 days after the initial settlement agreement execution.
Outcome: Reversed for appellant.
A. J. Chromy Construction Co. v. Commercial Mechanical Services, Inc.
What happened
The facts of the case, in plain language.
Integrity, as surety, was compelled under the performance bond to complete the construction contract after Commercial became insolvent and defaulted.
The settlement agreement executed October 6, 1975, expressly required delivery of a certified city council resolution approving and confirming the agreement as a condition of its effectiveness.
The city council adopted a resolution on October 27, 1975, approving and ratifying the settlement agreement that had been executed on October 6.
Chromy filed written notice of its claim on January 12, 1976, within 90 days of October 27 but not within 90 days of October 6.
What the court decided
The general contractor Commercial became insolvent and the surety Integrity completed a construction project for Montgomery. Integrity negotiated a settlement agreement with the city, executed October 6, 1975, but conditioned on city council approval. The city council approved the agreement October 27, 1975. Chromy, a subcontractor with an unpaid claim, filed notice January 12, 1976—timely (77 days) from October 27 but overdue (98 days) from October 6. The trial court deemed October 6 the acceptance date and dismissed the claim. The Minnesota Supreme Court reversed, holding October 27 was the statutory acceptance date because the October 6 agreement was expressly conditional on council approval. The court rejected the argument that a backdated completion date could shorten the notice period.
- Under a public construction performance bond statute requiring claims to be filed within 90 days of completion and acceptance by the proper public authorities, the acceptance date is the date on which the public authority unconditionally approves the agreement; where the initial written agreement is expressly conditioned on subsequent council ratification, the council's ratification date—not the earlier conditional execution date—triggers the notice period. (*582)
- Contracting parties to a public construction agreement may not backdate the date of acceptance in a manner that shortens or eliminates the statutory notice period for laborers and materialmen who are not privy to the contract. (*582)
- Summary judgment is a proper procedural vehicle when the operative facts are undisputed and the only question is the application of unambiguous statutory language to those facts.
How the court reached its decision
The court's reasoning, step by step.
Whether the date of statutory acceptance under Minn.St. 574.31 was October 6, 1975 (conditional execution of the settlement agreement) or October 27, 1975 (city council ratification). Paragraph 3 of the October 6 settlement agreement expressly required the city to deliver a certified copy of the council resolution 'approving, ratifying and confirming' the agreement, demonstrating the agreement was conditional on its face. The council's October 27 resolution referred to the same document as a 'proposed agreement' that was 'hereby approved'—present-tense language confirming that unconditional acceptance had not occurred before that date. Chromy's January 12, 1976 filing was 77 days after October 27, within the 90-day period. October 27, 1975 was the date of statutory acceptance under § 574.31; Chromy's notice of claim was timely.
Whether the contractually backdated completion and acceptance date of July 15, 1975 controls the running of the 90-day notice period under § 574.31. Integrity and the city agreed to deem July 15, 1975 the project completion and acceptance date. Adopting that backdated date would have eliminated the 90-day window entirely for Chromy, a subcontractor not party to the settlement. Such a result would nullify the legislative protection § 574.31 affords laborers and materialmen on public works projects. The July 15 backdated date does not control; parties cannot contractually extinguish the statutory notice rights of non-party laborers and materialmen.
Whether the September 2, 1975 city council meeting constituted statutory acceptance sufficient to start the 90-day notice period. The September 2 meeting minutes show the council approved certain payment amounts from minor subcontractors and a $1,100 payment from Integrity, but contain nothing indicating that a full and complete settlement agreement was presented, adopted, or ratified at that meeting. The September 2 council meeting did not constitute statutory acceptance; that date does not trigger the 90-day notice period.
Key quotes from the opinion
Notable passages from the opinion, in the court's own words.
Cases the court relied on
Earlier decisions the court cited as authority for its ruling.
Full opinion
The complete text of the court's opinion as published.
Opinion
Commercial Mechanical Services, Inc., contracted to perform construction services for the city of Montgomery. A. J. Chromy Construction Company entered into a subcontract agreement with Commercial. Integrity Mutual Insurance Company provided a surety bond to the city of Montgomery covering the contract with Commercial. Commercial became bankrupt and defaulted on the contract. Integrity completed the construction contract and entered into a settlement agreement with the city which was signed on October 6, 1975, and ratified by the Montgomery City Council on October 27, 1975. Chromy filed a claim against the bond on January 12,1976, which was within the 90-day statutory period for the October 27 date, but outside the 90-day period as to the October 6 date. The trial court granted Integrity’s motion for summary judgment. We reverse.
Although the exact amount of the claim is in controversy, the facts essential to this case are not in dispute. Commercial, the general contractor, became insolvent and Integrity was compelled under its surety bond to complete the contract with the city. At that time, Chromy had an unpaid claim against Commercial for services rendered under the subcontract between them. Integrity, as surety, was advised of this fact by letter in January of 1975.
Although the city had occupied the new building in the fall of 1974, a dispute arose between Integrity and the city as to whether the construction was in fact completed according to the terms of the construction contract. This dispute continued unresolved until August 1975, when an agreement of settlement was negotiated by Integrity and the city. The agreement provided among other things that May 15, 1975, would be deemed the date of the project’s completion and formal acceptance by the city. At a September 2, 1975, council meeting, a resolution was adopted approving a settlement payment of $1,100 from Integrity and additional sums from others in lieu of certain remedial construction work. There was no additional reference made to the proposed settlement agreement at this meeting other than to instruct the city attorney to get signed agreements from the parties.
Thereafter, the proposed settlement agreement was revised by the parties’ attorneys to change the May 15 purported completion and acceptance date to July 15, 1975. The revised agreement was forwarded to the city on September 25 and executed by the mayor and clerk on October 6, 1975. Paragraph 3 of the October 6 agreement provides:
“3. Montgomery agrees forthwith, upon the execution hereof, to deliver to Integrity the retainages and contract balance due on the Agreement in the amount of $21,233.80 together with a certified copy of the resolution of the Montgomery Council approving, ratifying and confirming this document.” (Italics supplied.)
On October 27, 1975, the city council adopted the following resolution:
“BE IT RESOLVED:
*581 “That the proposed agreement made and entered into by and between the City of Montgomery and Integrity Mutual Insurance Company is hereby approved and the appropriate officers of the City of Montgomery are authorized and instructed to execute the same by and in behalf of the City of Montgomery. A copy of said agreement is attached hereto and made a part hereof.” (Italics supplied.)
On January 12, 1976, Chromy filed its written claim on the bond with the county auditor pursuant to the provisions of Minn.St. 574.31. 1 January 12 is 98 days after October 6, but 77 days after October 27. Based on these facts, the trial court held the statutory date of acceptance to be' October 6, 1975, and granted Integrity’s motion for summary judgment on the ground that Chromy’s claim against the bond had not been timely filed under the statute and was therefore barred. A motion to vacate the judgment was denied and Chromy appealed.
The issues on appeal are:
(1) Were there factual disputes which made the entry of summary judgment improper?
(2) Was Chromy’s notice of January 12, 1976, timely as a matter of law?
1. Chromy argues that because a ruling on the timeliness of its notice of claim involved the resolution of factual issues, the trial court should not have considered Integrity’s motion for summary judgment. We disagree. As we noted above, the operative facts of this litigation are not disputed. In its ruling, the trial court had only to apply the pertinent language of Minn.St. 574.31 to the undisputed facts. Summary judgment was a fully appropriate procedural vehicle for the consideration of that question.
2. Considering the second issue raised on this appeal, we commence with the basic proposition that the purpose of the statute requiring performance bonds on public projects is—
“ * * * to protect laborers and ma-terialmen who perform labor or furnish material for the execution of a public work to which the mechanic’s lien statute does not apply.” Ceco Steel Products Corp. v. Tapager, 208 Minn. 367, 370, 294 N.W. 210, 212 (1940).
See, Weyerhaeuser Co. v. Twin City Millwork Co., 291 Minn. 293, 301, 191 N.W.2d 401, 405 (1971); Wheeler Lumber B. & S. Co. v. Seaboard Surety Co., 218 Minn. 443, 449, 16 N.W.2d 519, 522 (1944).
Mindful of the purpose underlying § 574.-31, we must examine the four dates which could, under the facts of this case, be deemed the date of acceptance which began the running of the statutory period for filing claims. The possible dates are July 15, 1975, September 2, 1975, October 6, 1975, and October 27, 1975.
The settlement agreement ultimately entered into between Integrity and the city purported- to backdate the official completion and acceptance of the new construction to July 15, 1975. Integrity argues that this date should control for the purposes of § 574.31 — a position which the trial court correctly rejected. Adoption of Integrity’s argument in theory would allow the parties to a construction contract to backdate acceptance far enough to actually eliminate *582 the 90-day notice period and thereby bar any claims against the performance bond. It is hornbook law that no one by contract may barter away the rights of persons not privy to the contract. To hold otherwise in this case would seriously diminish the protection which the legislature has afforded laborers and materialmen in § 574.31.
This precise question was considered by the Oregon Supreme Court in Virginia Glass Products Corp. v. Glens Falls Ins. Co., 254 Or. 340, 460 P.2d 858 (1969). In that case, the Oregon State Board of Control adopted a resolution on February 24 which retroactively accepted construction of a state building as of February 4, the final inspection date. Pursuant to the Oregon statute, a materialman filed a notice of claim which was timely with respect to a February 24 acceptance, but tardy under a February 4 acceptance. The court said (254 Or. 343, 460 P.2d 859):
“ * * * [^] public body may not retroactively start the time running. To hold otherwise would be to open the door for a public body to circumvent the statute.”
We agree.
Likewise, the statutory acceptance of the new construction did not occur on September 2,1975. Examination of the minutes of the September 2 city council meeting re- • veals that the council accepted the payment of certain sums from two minor subcontractors and a $1,100 payment from Integrity in lieu of certain remedial construction work. However, the minutes contain nothing which would indicate that any semblance of a full and complete settlement agreement was either presented, adopted, or ratified at the September 2 meeting.
Of the two remaining dates, the trial court found that October 6 rather than October 27 was the date of the city’s acceptance. In so doing, the court applied the language of § 574.31 to a set of undisputed facts. Therefore, its conclusion was one of law and does not bind this court. In re Trust Known As Great Northern Iron Ore Properties, 308 Minn. 221, 243 N.W.2d 302 (1976); Southern California Edison Co. v. State Bd. of Equal., 7 Cal.3d 652, 102 Cal.Rptr. 766, 498 P.2d 1014 (1972). We think the trial court incorrectly applied § 574.31, and that October 27 must be deemed the date of statutory acceptance.
In arriving at this conclusion, we note first that the agreement of October 6 was clearly conditional. Paragraph 3 of the agreement, previously quoted, required a certified copy of the resolution of the council “approving, ratifying and confirming” the agreement. Integrity, as a party to the contract, obviously felt this was an additional necessity. Even more illustrative of the conditional nature of the October 6 execution is the subsequent action of the Montgomery City Council. At the October 27 meeting, the matter was submitted to the council as a “proposed agreement.” The resolution of the council, previously quoted, states that “ * * * the proposed agreement * * * is hereby approved.” The language is most clear. As of October 27, the agreement executed on October 6 was still in the form of a proposal. The action of the city council on October 27 was phrased in the present tense. Anyone examining these records would have to be privy to inside information in order to conclude that the date of acceptance was not October 27. 2 Thus, we hold that the date of acceptance was October 27, 1975, and that Ghromy’s filing of the claim was timely under § 574.31.
The judgment in favor of Integrity is vacated and the matter remanded to the trial court for further proceedings consistent with this opinion.
. Minn.St. 574.31 provides as follows: “No action shall be maintained on any such bond . unless within 90 days after the completion of the contract and acceptance thereof by the proper public authorities, the claimant shall file a written notice specifying the nature and amount of his claim and the date of furnishing the last item thereof, in the office of the commissioner of insurance, in case the contract is for the performance of work for the state or any department thereof, and, in case the contract is let by any county, municipal corporation, or other public board or body, then such notice shall be filed in the office of the auditor of the county letting the contract or the county in which such municipal corporation, public board or body is situate, and if situate in two or more counties, then such notice shall be filed in the office of the auditor of each county; nor unless the action is begun within one year after the filing of such notice. * * * ”
. Indeed, in a phone call to the city clerk’s office, Chromy’s counsel was specifically informed that acceptance had occurred on October 27.
Continue your research
- Minnesota cases construing Minn.St. 574.31 to determine the date of formal acceptance for public construction performance bond claims
- Cases in other jurisdictions applying the rule that public bodies may not retroactively backdate construction acceptance to shorten bond notice periods
- Secondary sources on performance bond claim procedures and timeliness requirements for subcontractors on public works projects
Case-law data current through December 31, 2025. Source: CourtListener bulk data.