Builder's Risk Soft-Cost Check
Compare caller-supplied expected and observed records for builder's risk soft-cost check.
Description
Builder’s-risk soft-cost coverage can be inventoried by named requested and included cost categories.
Builder’s-risk soft-cost coverage can be inventoried by named requested and included cost categories. The percentage measures requested categories matched.1
Compare caller-supplied expected and observed records for builder's risk soft-cost check.
When to use Builder's Risk Soft-Cost Check
Use this tool to compare caller-supplied expected and observed records for builder's risk soft-cost check.
Prepare the supplied policy terms, dates, assumptions or recorded indicators requested. Keep monetary amounts on one currency basis and select the applicable thresholds separately.
How to use Builder's Risk Soft-Cost Check and understand its results
- Prepare the supplied policy terms, dates, assumptions or recorded indicators requested. Keep monetary amounts on one currency basis and select the applicable thresholds separately.
- Enter requestedSoftCosts, includedSoftCosts using the field table and calculation rules, then run the tool.
- Read coveragePercent, matched, missing, unexpected. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| requestedSoftCosts | Requested soft costs | list of string | Required |
| includedSoftCosts | Included soft costs | list of string | Required |
Supply requested soft-cost labels first and included labels second. Trim and lowercase labels; reject blanks and require a nonempty first list. Deduplicate by normalized key, retaining first position and last trimmed spelling. Return matches/missing first-list labels, unexpected second-list labels, and percentage; the second list may be empty.
coverage%=100×matchedUnique/requiredUnique Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| coveragePercent | Coverage (%) | number; minimum: 0; maximum: 100 |
| matched | Matched items | list of string |
| missing | Missing items | list of string |
| unexpected | Unexpected items | list of string |
{
"input": {
"requestedSoftCosts": [
"design fees",
"permits",
"interest"
],
"includedSoftCosts": [
"design fees",
"permits"
]
},
"output": {
"coveragePercent": 66.66666666666666,
"matched": [
"design fees",
"permits"
],
"missing": [
"interest"
],
"unexpected": []
}
}Limitations and assumptions
No policy, delay cause, deductible, limit or actual covered expense is interpreted.
Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Lists are limited to 100,000 entries; the rules above may require smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Title Policy Scope Comparison: Compare caller-supplied expected and observed records for title policy scope comparison. For a complementary task, use Recall Loss Split: Split product-recall loss across supplied coverage limits.
References
-
Builder's Risk Soft-Cost Check — tool.io
Similar or alternative tools
- Title Policy Scope Comparison
Compare caller-supplied expected and observed records for title policy scope comparison.
- Recall Loss Split
Split product-recall loss across supplied coverage limits.