Why are banks adopting BRAVE instead of using their own custom Excel appraisal templates?

Custom per-bank Excel templates force appraisers to maintain a different format for every lender they serve, raise the error rate, and require each bank to build and maintain proprietary parsers. BRAVE collapses that into a single 99-field standard validated at usebrave.org, so the appraiser delivers the same file format to every BRAVE-adopting lender and each lender ingests via one shared schema. The economics favor BRAVE once a bank's appraisal volume is high enough to justify migration cost.

BRAVE vs Custom Bank Excel Templates

The Problem BRAVE Solves

Until recently, every commercial real estate lender requesting structured appraisal data on top of the PDF report had to either:

Hand-key numbers from the PDF into the bank's loan origination system, or
Issue a custom Excel template to each appraiser, define the fields, and parse the returned files into the LOS.

Most banks did some combination of both. The result: appraisers serving 8 banks maintain 8 different Excel templates, each with subtly different field names, data types, and conventions. Bank credit teams maintain 8 different parsers. Errors compound. Onboarding new appraisers is slow.

BRAVE — the Banking Real Estate Appraisal Valuation Exchange — collapses this into a single 99-field schema shared across every adopting lender.

Side-by-Side

Dimension	Custom bank Excel	BRAVE
Format consistency across lenders	None — each bank differs	Single shared schema
Field naming	Bank-defined	Open spec at usebrave.org
Data type enforcement	Varies by bank	Defined per field (Int32, Decimal, Date, etc.)
Validation	None or bank-specific	Free public validator at usebrave.org
Appraiser cost	Maintain N templates for N banks	Maintain one
Bank cost (build)	Build + maintain a parser	Use shared schema
Bank cost (run)	High error rate, manual cleanup	Lower error rate, automated ingestion
New-bank onboarding	Distribute template, train appraisers	Reference usebrave.org
New-appraiser onboarding	Train per template	Train once on the standard
Cross-bank loan participations	Translate between templates	Same file shared

What Custom Excel Templates Look Like

A typical bank custom template includes:

A cover sheet with the bank's branding and instructions
20–60 fields the bank cares about (often a subset of what BRAVE covers — 99 fields is the result of consolidating across many banks' wishlists)
Bank-specific formatting (currency display, date format, percentage decimals)
Sometimes calculation helpers or input validation in-sheet
A separate tab for sales comparables (highly variable structure)

Distributed via email or a vendor portal. Returned as filled-out XLSX. Parsed by a bank-internal tool — sometimes a one-off Excel macro, sometimes a more robust ETL script.

Where the Costs Pile Up

For the appraiser

Maintenance overhead: when a bank updates its template, every assignment in flight has to be re-checked.
Format errors: typing "Yes" vs "yes" vs "Y" in different fields, dates as MM/DD/YYYY vs ISO, percentages as 0.06 vs 6 vs "6%" — every variation is a future revision request.
Workflow overhead: choosing the right template for each assignment based on the lender.
Per-bank QC: re-checking against each bank's idiosyncratic rules.

A senior commercial appraiser running 80 assignments a year across 6 banks might spend 80–120 hours/year purely on template overhead.

For the bank

Parser maintenance: every template change requires a parser update.
Manual cleanup: rejected/malformed submissions go back to the appraiser, delaying loan close.
Per-appraiser onboarding: each new appraiser needs training on the bank's template.
No interoperability: a participation loan or a sale of the loan to another bank doesn't carry the structured data forward.
Skill concentration: only one or two people in the credit team know how to read the template; key-person risk.

For the borrower

Slower closings because of revision cycles
Higher all-in cost as appraiser fees absorb template overhead

How BRAVE Changes the Economics

Once a critical mass of banks adopts BRAVE (which is the open question right now — Bank OZK is currently the only bank with a hard requirement), the per-bank template economics shift:

The appraiser writes the BRAVE file once and delivers it everywhere
Banks ingest using a single schema, with a free public validator catching most errors before submission
Cross-bank workflows (participations, syndications, sales) carry structured data forward
New appraiser onboarding becomes "follow the spec at usebrave.org"

Banks that previously built and maintained custom templates can deprecate that infrastructure. The breakeven point — when BRAVE migration cost exceeds the ongoing custom-template cost — is hit faster at higher appraisal volume.

When Custom Excel Still Makes Sense

Custom templates aren't going away tomorrow:

Niche fields: a bank that cares about a non-BRAVE field (e.g. a CMBS-specific covenant) still needs custom collection for that field.
Sales comparable data: BRAVE captures appraisal output, not the underlying comp set. Banks that want structured comp data still need a separate template or extraction step.
Pre-BRAVE legacy portfolios: existing loans were underwritten on the old template; some banks keep collecting the same template to maintain comparability.
Low-volume lenders: a bank doing 30 CRE appraisals a year may not be worth the migration cost.

What This Means for Appraisers

If you serve a mix of BRAVE-required, BRAVE-supporting, and custom-template lenders today:

Produce BRAVE for the lenders that require or accept it
For custom-template lenders, derive their template from your BRAVE file rather than reproducing it from scratch — most custom fields are a subset of BRAVE
Track which lenders are moving to BRAVE so you can deprecate templates from your side

For the full BRAVE field catalog, see 99-fields reference. For the standardized validation rules, use the BRAVE validator at usebrave.org.

BRAVE vs Custom Bank Excel Templates