Chapter 11
Case Scenarios & Examples
Worked examples showing how bond requirements arise and change across real project situations.
Topics in this chapter
11.01
Case Scenario: A Contractor Preparing for a Government BidA hypothetical contractor reviews bidding documents, finds that Bid Security is required, and works out whether a surety bond is a permitted form of it before preparing an inquiry.
11.02
Case Scenario: A Contractor Wins a Major Project—What Happens Next?A hypothetical contractor is awarded a major project and finds that Performance Security is required at the contract stage — a requirement that is not automatically the same thing as a performance bond.
11.03
Case Scenario: An Advance Payment Requires a BondA hypothetical contract provides for an advance payment and requires corresponding security. The applicant works out what the contract actually requires before requesting anything.
11.04
Case Scenario: A Project Enters the Warranty PeriodA hypothetical project reaches completion and moves into a warranty, maintenance or defects-liability stage in which the governing agreement requires security for specified post-completion obligations.
11.05
Case Scenario: A Supplier Is Asked for a Performance BondA hypothetical supplier enters a private supply agreement in which the purchaser requires a performance bond, showing that surety requirements arise well outside construction and public procurement.
11.06
Case Scenario: A Growing Contractor Has Several Ongoing ProjectsA hypothetical contractor with several projects already running seeks a bond for another one. The Surety looks at the new obligation alongside everything already committed.
11.07
Case Scenario: Additional Documents Are Requested by the SuretyA hypothetical applicant receives a request for clarification and further documents part-way through an evaluation. The request is neither an approval nor a decline.
11.08
Case Scenario: A Bond Requirement Changes Before SubmissionA hypothetical applicant learns that the bond requirement has changed before submission. The task is to verify the change from the authoritative source and work out its effect through the proper channel.
Important Notice
Inquiries and supporting documents submitted through SuretyPH may be referred to the applicable participating insurer for evaluation. Submission does not constitute approval or issuance of a surety bond. Applications are subject to the insurer's requirements, evaluation, underwriting, terms, conditions, and approval.
SuretyPH is a digital platform for surety bond information, inquiries, requirements and request tracking. It does not underwrite, approve, bind, issue, or guarantee any insurance policy or surety bond. Evaluation, underwriting, approval, pricing and issuance are undertaken by the applicable licensed insurance company.