From brochure to property card, with the page it came from

Feature · Documents become records

A developer sends a 40-page brochure to the group. Ten minutes later the broker has a card: project, unit types, prices, payment plan, handover date, service charge, and a link from every figure to the exact page of the PDF. Nothing is retyped and nothing is guessed.

What the card contains

Why evidence matters

In off-plan the details decide the deal: which instalment is due at handover, whether the price includes the DLD fee, which units are still available. A card that shows the page beside the number lets the broker answer with confidence and lets the client verify.

Brokbase treats a document as untrusted input: it is archived first, parsed in a sandbox, and the model is only allowed to publish a value that it can quote. Low-confidence pages are flagged for a human look instead of being published.

Photos, plans and scans

Floor plans and renders are kept with the card and can be sent to a client on request. Scanned documents without a text layer are marked for review; optical recognition is switched on per company when it is needed, never silently.

Questions people ask

Which formats are supported?

PDF brochures, price lists and payment plans, plus JPG and PNG images. Very large files are archived and read in bounded steps.

What happens when two brokers receive the same brochure?

The same document is recognised by its checksum and read once per identical file; each company still sees only its own copy.

Can I edit a card?

Yes. Brokers correct and complete cards in the workspace; the evidence links stay attached to the values that came from the document.

Read next

Request access