Availability: Arranged through sales
What comes back from a BPS engagement, and how you know what happened to every document.
The geometry
Consolidated DXF and or GeoJSON for the processed backlog, in the coordinate reference confirmed against your GIS during discovery. Other formats and custom output structures are set in scoping; where the deliverable is a system rather than a file set, the engineering team builds to that requirement.
The processing report
Every batch ships with a report listing each document and what happened to it: processed, its confidence tier, and any flag that kept it from processing (unsupported description class, unreadable source, missing identifier).
How to read the confidence tiers
Each plotted result carries a confidence score from the pipeline, and the tiers route the review work. Higher tiers typically need little to no human interaction; lower tiers route to human review first, riskiest plots first. What moves the score: source document quality, description complexity, and how much reference parcel data was available for placement. A score is the model’s own estimate rather than a verification of correctness, which is exactly why review runs in confidence order instead of being skipped.