Technology

How Brokredge decides what is true.

A language model will always produce an answer. The engineering around it decides whether that answer may be sent to a client. This is what that engineering does.

Provenance

Every fact carries four things, not one.

A figure on a screen is not information. A figure, a document, a date and a confirmation is.

The document it came from

the file itself, by name and content hash, so the same file uploaded twice is one document, not two agreeing sources

The date the document states

an issue or as-of date read from the document, not the day it happened to be uploaded

When it reached Brokredge

kept separate, and never used to make an old figure look fresh

When a person last confirmed it

a human confirmation outranks paper, and is recorded with who and when

Price

AED 2,380,000

Developer price list · issued 1 Sept · uploaded today · never independently verified · matches 2 other sources

Conflict engine

When documents disagree, evidence decides — and the agent still sees the disagreement.

Brokredge never silently picks a value. It ranks the evidence, shows the alternatives, and says which source is newest so a broker can verify before quoting.

01

Dated evidence beats undated

A sheet that says when it was issued outranks one that does not.

02

The latest as-of date leads

Between two dated documents, the newer one becomes the current answer.

03

Identical copies are not corroboration

The same file forwarded three times is one source. Agreement is counted by content, not by count.

04

Different kinds of document are compared carefully

A brochure and a price list can hold different values for the same field without either being wrong; commercial sheets are compared with commercial sheets.

05

A person can settle it

When a broker confirms a value, that becomes the answer — and the disagreement stays visible in the record.

⚠ Conflicting handover information — 3 sources disagree. Latest source says March 2028 — verify before quoting.

Q4 2027 — developer brochure · issued 16 Mar

Q1 2028 — developer price list · issued 3 Aug

March 2028 — developer availability sheet · issued 1 Sept

Quoteability policy

Not every fact on file may be sent to a client.

Age is judged from the document's own date, and the window depends on what the fact is and where it came from. Availability goes stale in hours; a floor area does not go stale at all.

FactSourceQuoteableAfter that
AvailabilityDeveloper price list, availability sheet, CSV exportquote within 24 hourswarn to 48 hours, then blocked
AvailabilityAgent note, undated or other documentquote within 12 hourswarn to 24 hours, then blocked
PriceDeveloper price list, availability sheet, CSV exportquote within 3 dayswarn to 7 days, then blocked
PriceAgent note, undated or other documentquote within 24 hourswarn to 3 days, then blocked
Payment plan, handover, service chargeany sourcequoteablewarned once past its window
Size, layout, view, floorany sourcequoteablestructural facts do not go stale
QuoteableWarn before quotingBlocked — conflicting or expired

A human confirmation resets the clock: once a broker confirms a figure, it is treated as a primary source from that moment.

Extraction

Honest about what a model does.

Reading a document is not deterministic: the same PDF can produce a slightly different result on a different run. We do not pretend otherwise. Every extraction stores the model, the prompt and schema version, the time it ran and the hash of the file it read, so any answer can be traced back and re-checked against the source.

That is also why a person can confirm a value, and why confirmation outranks extraction.

Release discipline

Nothing significant changes silently.

Every version ships with a build report generated from a clean tree: the unit tests, the evaluation cases and an extraction benchmark all run against the exact commit that gets tagged.

Reliability is tested against a written protocol — deliberately messy documents, duplicate files, superseded price lists and conflicting sheets — before anything reaches a brokerage.

Boundaries

What Brokredge does not do.

No portal scraping

Brokredge reads what the brokerage already has. It does not take listings or contacts from property portals.

No owner-contact trade

Owner or client contact details are never sold, resold or enriched.

No price prediction

Brokredge reports what documents say. It does not forecast prices or value a property.

No legal or valuation advice

It states figures and their sources. Decisions stay with the broker.

No silent answers

If nothing on file states a fact, the answer is “not on file”, with what to upload.

Test it against your messiest project.

The one with three price lists, two brochures and a WhatsApp forward. That is the interesting case.