Title Policy Scope Comparison

Compare caller-supplied expected and observed records for title policy scope comparison.

Description

Owner and lender title-policy risk labels can be compared to see which supplied owner-policy risks also appear in the lender list.

Owner and lender title-policy risk labels can be compared to see which supplied owner-policy risks also appear in the lender list. Coverage is directional.1

Compare caller-supplied expected and observed records for title policy scope comparison.

When to use Title Policy Scope Comparison

Use this tool to compare caller-supplied expected and observed records for title policy scope comparison.

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 Title Policy Scope Comparison and understand its results

  1. Prepare the supplied policy terms, dates, assumptions or recorded indicators requested. Keep monetary amounts on one currency basis and select the applicable thresholds separately.
  2. Enter ownerPolicyRisks, lenderPolicyRisks using the field table and calculation rules, then run the tool.
  3. Read coveragePercent, matched, missing, unexpected. The explanation below defines the units, signs, ordering and any flags or placeholder values.
  4. 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 fieldMeaningValue type; see rules belowRequirement
ownerPolicyRisksOwner-policy covered riskslist of stringRequired
lenderPolicyRisksLender-policy covered riskslist of stringRequired

Supply owner-policy risks as the first list and lender-policy risks as the 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 fieldMeaningValue type
coveragePercentCoverage (%)number; minimum: 0; maximum: 100
matchedMatched itemslist of string
missingMissing itemslist of string
unexpectedUnexpected itemslist of string
json
{
  "input": {
    "ownerPolicyRisks": [
      "ownership defect",
      "prior lien",
      "forgery"
    ],
    "lenderPolicyRisks": [
      "prior lien",
      "forgery"
    ]
  },
  "output": {
    "coveragePercent": 66.66666666666666,
    "matched": [
      "prior lien",
      "forgery"
    ],
    "missing": [
      "ownership defect"
    ],
    "unexpected": []
  }
}

Limitations and assumptions

No title search, policy text, ownership defect or actual protection is evaluated; reversing lists changes the percentage basis.

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 Social Engineering Coverage Gap: Compare caller-supplied expected and observed records for social engineering coverage gap. For a complementary task, use Builder's Risk Soft-Cost Check: Compare caller-supplied expected and observed records for builder's risk soft-cost check.

References

  1. Title Policy Scope Comparison — tool.io

Similar or alternative tools

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies