In this construction contract dispute, Western Surety Company and Continental Casualty Company (the “Sureties”) appeal from the trial court’s grant of partial summary judgment to defendant State of Georgia Department of Transportation (the “DOT”) on the Sureties’ claims for breach of contract and violation of the Georgia Prompt Pay Act (the “PPA”).1 The Sureties contend that the trial court erred in entering partial summary judgment because there remain genuine issues of material fact. For the reasons set forth below, we disagree and affirm.
Summary judgment is warranted when the moving party shows that there is “no genuine issue of material fact and that the movant is entitled to judgment as a matter of law.”2 A defendant may meet this burden by demonstrating that “the documents, affidavits, depositions and other evidence in the record reveal that there is no evidence sufficient to create a jury issue on at least one essential element of the plaintiff’s case.”3 And when the moving party discharges this burden, “the nonmoving party cannot rest on its pleadings, but must point to specific evidence giving rise to a triable issue.”4 We review a grant or denial of summary judgment de novo and construe the evidence in the light most favorable to the nonmovant.5
So viewed, the record shows that the DOT and Bruce Albea Contracting, Inc. (“BAC”) entered into a construction contract (the “Contract”) for work on roadway US 27 (the “Project”). The Sureties issued performance and payment bonds to the DOT, as obligee. The completion date for the Project was originally March 31, 2007, but was extended to January 18, 2008.
*672After BAC entered into the Contract, it experienced an increase in material costs for the Project. As a consequence of the increase in material prices, particularly for asphalt and other petroleum-related products, BAC suffered financial difficulties. In December 2006, BAC notified the Sureties of the problem.
Rather than allow the Project to “grind to a halt,” the Sureties provided funds to BAC between April and July 2007. In exchange for their help with the Project, BAC provided the Sureties with a letter from BAC to the DOT, dated April 18, 2007, stating that BAC could not perform the work and was voluntarily abandoning the Contract. The letter was received by the DOT in late June 2007, and the DOT placed BAC in default and directed the Sureties to take over the work on the Project.
On September 11,2007, the Sureties sent two claim letters to the DOT. After a meeting, the DOT asked for additional information. The Sureties chose not to respond to the DOT’s request and subsequently sued the DOT, setting forth three counts of breach of contract6 and one count of violation of the PPA. The DOT moved for partial summary judgment on the Sureties’ claims for: (i) compensation for price inflation incurred after March 31, 2007 (the “Original Completion Date”) (“Count II”); (ii) compensation for price inflation incurred before the Original Completion Date (“Count III”); and (iii) violation of the PPA.7 The trial court granted the DOT’s motion for partial summary judgment. On appeal, the Sureties contend that the trial court erred in granting summary judgment on Count II and Count III because they did not waive their claims against the DOT by failing to strictly comply with the Contract’s notice and claim provisions.8 The Sureties also contend that the trial court erred by finding that they are barred from recovering attorney fees under the PPA.
1. The Sureties acknowledge that neither BAC nor the Sureties strictly followed the claim notice requirements set forth under the *673Contract, particularly Specification 105.13. Specification 105.13.B.9 provides:
NOTICE OF POTENTIAL CLAIM: In any case in which the Contractor believes that it will be entitled to additional compensation, the Contractor shall notify the Engineer in writing of its intent to claim such additional compensation. Such notice shall be given in order that the Department can assess the situation, make an initial determination as to who is responsible, and institute appropriate changes or procedures to resolve the matter.
a. Claims for Delay — The Department shall have no liability for any delay which occurred more than one week prior to the filing of such written notice. Failure of the Contractor to give such written notice in a timely fashion will be grounds for denial of the claim.
b. All Other Claims Except Acceleration and Delay — If the Contractor does not file such written notice before beginning the work out of which such claim arises, then the Contractor hereby agrees that it shall have waived any additional compensation for that work and the Contractor shall have no claim thereto.9
In submitting a claim, the Contractor is also required to provide certain information, as set forth in Specification 105.13.C, and to certify the claim, as required by Specification 105.13.D.
Further, under Specification 105.13.B.6.b, recoverable damages under the Contract include “[documented additional costs for materials.” The parties also agreed under Specification 105.13.B.5, however, that “[cjompliance with the provisions of this Subsection will be an essential condition precedent to any recovery of damages by the Contractor.”
Parties to construction contracts are free to enter into claim notice requirements, and such provisions are “legal and binding on the parties in the absence of special circumstances,” which may include waiver or estoppel.10 Thus, we start with the premise that the *674Contract is enforceable and that the Sureties cannot recover on their claims for damages under Count II and Count III, absent special considerations. The Sureties argue that those considerations are present here, and that a jury could conclude that (i) the DOT waived strict compliance with Specification 105.13, (ii) BAC and the Sureties reasonably and substantially complied with the notice and claim procedures, (iii) the DOT had actual notice of BAC’s and the Sureties’ claims, and (iv) the DOT was not prejudiced by the lack of strict compliance. It follows, they contend, that it was error for the trial court to grant partial summary judgment to the DOT on Count II and Count III. We disagree.
(a) The Sureties contend that the DOT waived strict compliance with the notice and claim procedures under the Contract by actively encouraging disputes to be handled informally and by punishing those who followed the strict claims procedures, by granting extensions of the contract time, and by negotiating with the Sureties. In that respect, we have “recognized that a party to a contract may waive contractual provisions for his benefit.”11 And in the context of claim notice requirements, “[c]ourts will readily seize upon any fact or circumstance growing out of the conduct of the parties, tending to show a waiver of strict compliance, and will seek to avoid the forfeiture and to leave the actual merits of the case open to investigation.”12 However, “mere silence when there is no duty to speak, cannot constitute a waiver or estoppel.”13
To show that the DOT had encouraged disputes to be pursued outside the parameters of the Contract, the Sureties point to evidence that before 2006 or 2007 the DOT had a general practice of discouraging contractors from filing notice of claims but then retrospectively considering requests for additional compensation.14 We are unpersuaded that what the DOT did at other times, with other parties, *675under different contracts, is relevant here. Although the Sureties suggested to the trial court that the course of dealing was so universal as to become part of the Contract by implication, the applicable agreement is set forth in the express provisions of the Contract.15
The Sureties also point to evidence that BAC’s principal, based on his experience with the DOT on other projects, was reluctant to file any claim against the DOT. BAC’s principal deposed that on another project, upon “issue[ ] [of] the word claim, [the DOT] immediately used my liquidated damages as leverage.” The DOT’s engineer on the Project also testified that as to another project he worked on with BAC’s principal, it was “not an out-of-question conversation” that he told BAC “we’re not going to give you time if you are asking for both time and money.” According to BAC’s principal, in this case BAC and its supplier wanted to “work out an escalation agreement” with the DOT, but wanted to “get the time extension first.”
While there is evidence that BAC was “afraid to ruffle the feathers” of the DOT by filing a claim, and that the DOT might react negatively if such a claim was made, the evidence tends to explain why the procedures for filing a claim under the Contract were intentionally not followed by BAC, not that the DOT waived any of the Contract provisions regarding the filing of claims.16 Rather, “[t]here is no evidence that DOT . . . did any affirmative act which would lead [BAC] to believe that it was not necessary for it to give timely notice of a claim.”17
The Sureties also point to the DOT’s alleged practice of “waiting until the end of projects to consider time extensions,” showing that in this instance the DOT considered and granted BAC’s requests for time extensions in 2007, notwithstanding that the delays occurred in 2004, 2005, and 2006. Therefore, the Sureties argue, because the *676requests for extensions were sent more than one week after the delays and were not in strict compliance with the notice requirements, there was evidence of waiver. The DOT shows, however, that extensions of contract time were not granted under the provisions at issue here.18 Thus, we cannot agree with the Sureties that they have pointed to evidence that the DOT thereby waived strict compliance with the claim notice requirements.
Last, the Sureties contend that the DOT waived strict compliance with the claim notice provisions by participating in settlement negotiations. However, the Sureties do not show that during any communications or discussions between the Sureties and the DOT, the DOT agreed or intimated that it would waive any of the Contract requirements. Even after the submission of the two September 11, 2007 claim letters, the DOT continued to request information and acts on the part of the Sureties which were consistent with an insistence of strict compliance with the terms of the Contract.
(b) The Sureties further contend that a jury could conclude that BAC and the Sureties reasonably complied with the notice and claim provision of the Contract. We disagree.
As a rule, “[a]ny notice requirement must be reasonably construed.”19 And substantial compliance with a notice provision may present an issue for the jury if “[t]he evidence... appears to be ‘in the spirit’ of the contract provision.”20
Here, the two September 11, 2007 letters asserted claims by the Sureties against the DOT for compensation for price escalations and damages under the Contract. Nevertheless, the letters were on their face untimely as to the majority of the claims set forth therein. As we noted supra, the parties had agreed under Specification 105.13.B.9 that “[t]he [DOT] shall have no liability for any delay which occurred more than one week prior to the filing of” the written notice of potential claim and that, as to other claims, “[i]f the Contractor does not file such written notice before beginning the work out of which such claim arises, then the Contractor hereby agrees that it shall have waived any additional compensation for that work.”
*677After the DOT received the two claim letters, it asked the Sureties, consistent with Specification 105.13.C for, among other things, “[a] copy of the ‘Notice of Potential Claim’ filed for each delay event or issue associated with claim.” The Sureties did not respond to this request, and the Sureties’ representative maintained in his deposition that they did not do so because the DOT “had their own project files” and because the DOT had adequate notice of the claims. On appeal, the Sureties point to informal discussions between BAC and the DOT and letters sent from BAC and the Sureties to the DOT and contend that they are sufficient to create an issue of material fact as to “whether BAC and the Sureties’ efforts were ‘in the spirit’ of” the Contract’s requirements. For example, the Sureties show that they sent the DOT a letter in July 2007 concerning price escalations, stating, “All rights and/or claims for increased compensation due to time extension(s) and/or escalation of oil and/or asphalt prices increases to [BAC] and/or [the Sureties] are reserved.” But the Contract does not reasonably contemplate that a contractor may unilaterally “reserve” a claim.21 Further, while these communications might show that the Project had been delayed and was subject to material price escalations, and that BAC sought an agreement with the DOT to provide relief, they did not alert the DOT that there were any grounds for a claim. For example, with respect to damages arising out of delay, Specification 108.07.E provides, in pertinent part, “[i]f the Engineer finds that The Work was delayed because of conditions beyond the control and without the fault of the Contractor, he may extend the time for completion in such amount as the conditions justify.” Thus, while a delay might be excusable, the Sureties do not show that the DOT was informed that the Sureties or BAC contemplated that the DOT was obligated to pay compensation for the delay, including damages for increased material costs. Rather, under Specification 105.13.B.2, the DOT “will be liable only for those delay damages caused by or arising from acts or omissions on the part of [the DOT] which violate legal or contractual duties owed to the Contractor by [the DOT]. The Contractor assumes the risk of damages from all other causes of delay.” Thus, we conclude that none of the communications by BAC or the Sureties to the DOT before the September 11, 2007 claim letters reasonably or substantially complied with the requirement that timely notice of a claim be given to the DOT.
*678The September 11, 2007 claim letters were perhaps sufficient to provide reasonable notice of a claim to the extent the notice was not untimely. However, in addition to notice, the parties agreed as to the required contents of a claim, including the information to be provided thereby.22 When the DOT requested that information in writing following the submission of the claim letters, the Sureties chose not to respond. According to the Sureties’ representative, the DOT’s letter was “a request for free discovery in litigation,”23 and “an excuse for . . . nonpayment.”24 The DOT also shows that the Sureties intentionally declined to comply with Specification 105.13.D regarding certification of the claim. The Sureties suggest that because the DOT had previously analyzed and granted requests for extensions in the Project completion date that the information contemplated by Specification 105.13.C was not needed by the DOT. But the parties had not contemplated that the DOT would independently gather all the documentation needed to assess a claim, or that a contractor could assume that the information it was required to produce in connection with a claim was already present in the DOT’s files. Given the foregoing, we cannot agree with the Sureties that a trier of fact could conclude that their efforts were “in the spirit” of the Contract.
(c) The Sureties further contend that a jury must decide whether the DOT had actual notice of BAC’s and the Sureties’ claims. They rely on APAC-Ga. v. Dept. of Transp.,25 where we found that “[t]he key issue is whether DOT had actual notice of the delays for which APAC seeks damages.”26 Here, the Sureties point out, the DOT had notice of delays and even granted extensions for the delays. We find APAC-Ga. to be distinguishable.
At issue in APAC- Ga. was whether the trial court erred in finding that the contractor failed as a matter of law to comply with a provision regarding the extension of contract time.27 And the evidence in that *679case showed that the contractor sent over 50 letters to the DOT giving notice of delays and the need for extensions, and that the DOT also granted extensions without request and failed to charge contractual liquidated damages for failure to complete the project on time.28
In this case, however, the DOT’s knowledge “that there were problems with [delays] is not tantamount to knowledge that [BAC or the Sureties were] incurring monetary damages or that [they] intended to file a claim.”29 If compliance with the Contract could be deemed waived or excused because the DOT was aware of a delay or of price escalations, which, as to the latter, would often be public knowledge, then “the provision requiring timely written [notice of a potential claim] would be meaningless and superfluous.”30 Similarly, to the extent that the DOT had actual knowledge of claims in light of the September 11,2007 claims letters, that did not leave the Sureties free to ignore the remainder of Specification 105.13.
(d) Last, the Sureties argue that a jury should consider whether the DOT was prejudiced by BAC’s and the Sureties’ failure to strictly comply with the Contract’s claim notice provisions. They acknowledge that “[n]o Georgia appellate court has made a determination whether prejudice is a necessary element to prevent waiver of strict compliance.” Rather, they rely on decisions of the General Services Administration Board of Contract Appeals.31 As the parties did not incorporate federal law under federal contract notice provisions into the Contract, we find that the authority relied on by the Sureties is not relevant or controlling.
In light of the foregoing, we conclude that there remains no issue of material fact as to whether BAC’s and the Sureties’ failure to comply with the claim notice provisions of the Contract was waived by the DOT, whether BAC or the Sureties reasonably or substantially *680complied with those provisions, or whether their compliance was excused by the DOT’s actual knowledge of a claim. It follows that the trial court did not err in granting partial summary judgment to the DOT on Count II and Count III.32
Decided March 28, 2014.
2. In Count IV of their complaint, the Sureties requested attorney fees and interest arising out of the DOT’s alleged violation of the PPA. Specifically, the Sureties alleged that the DOT violated the PPA “by failing to pay the Sureties within 15 days of receipt of Voucher #58.”33 The Sureties claim that the trial court erred in granting partial summary judgment to the DOT on this count. We disagree.
It is undisputed that the DOT’s payment for Voucher 58 has been acceptedby the Sureties. AndOCGA § 13-11-7 provides that “[acceptance of progress payments or final payment shall release all claims for interest on said payments.” Accordingly, the Sureties do not show that they have a claim for interest under the PPA with respect to the failure to timely pay Voucher 58.34
The Sureties argue that inasmuch as Voucher 58 was paid after the action to enforce a claim was instituted, the “Sureties are entitled to [attorney] fees incurred until the voucher was paid.”35 This assertion contradicts the complaint, which states that the DOT’s payment for Voucher 58 was received on January 15, 2008, before the complaint was filed on March 18, 2008. The affidavit which the Sureties reference as evidence of payment after the filing of the action simply states that the DOT “paid and the Sureties accepted Voucher 58.” As the record is inconsistent with the Sureties’ theory of recovery as to attorney fees, and the PPA contemplates attorney fees in actions to “enforce” a claim,36 we find no error in the trial court’s grant of summary judgment on this count.
Judgment affirmed.
Ellington, P. J., and Branch, J., concur.
*681 Thompson, Slagle & Hannan, Dewitte Thompson, Jr., Jefferson B. Slagle, for appellants.
Hall Booth Smith, Denise W. Spitalnick, for appellee.