UAD1316
FATALOfficial message text · Appendix H-1: UAD Compliance Rules — URAR, v1.5
Indicate whether the private street maintenance agreement exists.
Fatal — a single unresolved Fatal makes the entire submission come back NOT SUCCESSFUL (UCDP Hard Stop 401).
What triggers UAD1316
The published rule logic, verbatim:
If PropertyPrimaryEntryExitMethodType = "PrivateStreet" and PrivateStreetMaintenanceAgreementExistIndicator is not provided
- • Checked for the Subject property.
- • Bound to MISMO data point
PrivateStreetMaintenanceAgreementExistIndicatorat../VALUATION_ANALYSIS/PROPERTIES/PROPERTY/SITE/PROPERTY_ACCESS/PROPERTY_ACCESS_DETAIL/
How to fix it
On the URAR, this lives at: Site → Known Maintenance Agreement. Complete or correct that field in your form software, regenerate the package, and re-check before submission.
Because this is a Fatal edit, do not submit until it is resolved — one Fatal bounces the whole package.
UAD1316 is in UADCheck's reference library; automated coverage for it is on the roadmap. The inspection already runs the full GSE schema, the package-integrity layer, and every auto-checkable compliance rule — each report states exactly what was covered.
Begin inspection →Related messages
- UAD1278 FatalProvide a photo of the water frontage.…
- UAD1287 FatalProvide the type of property restriction.…
- UAD1288 FatalProvide a description when property restriction = 'Other'.…
- UAD1289 FatalProvide the easement type.…
- UAD1290 FatalProvide a description when easement = 'Other'.…
- UAD1291 FatalProvide the direction of the encroachment (i.e., bordering property en…
Source: Appendix H-1: UAD Compliance Rules — URAR, v1.5 (public GSE document). Verified against the published spreadsheet; not affiliated with Fannie Mae or Freddie Mac.