From backlog to delivery.
BPS is a partnership that starts with a pilot. Here is how an engagement runs, from your requirements to standardized outputs.
How an engagement runs
Five stations, from your requirements to delivery. The spec you set in the pilot is what everything downstream is built against.
- 01
Send your requirements.
Share sample documents and an output spec: formats, title blocks, naming, and coordinate system. That spec is what everything downstream is built against.
Customer specFormatsPDF · DXF · SHPTitle block[client template]Namingtract-{id}Coordinate system[EPSG code] - 02
Run a pilot together.
We process a pilot batch and review it side by side. You set the acceptance criteria, and every output carries a flagged-for-review count, because outputs are checked, not promised perfect.
Pilot manifestDocuments in50Outputs out50Flagged for review3 - 03
We build to your spec.
Once the pilot is accepted, we build the intake and output tooling around your exact requirements, so the run works the way you defined it.
config.ymlintakebatch/deedsoutput.formatspdf,dxf,shpoutput.namingtract-{id}crs[EPSG code] - 04
Bulk processing begins.
The backlog runs at volume against the agreed spec. Standardized outputs come through with their review flags intact.
Processing · in progress - 05
Delivery.
You receive standardized outputs and a delivery manifest with rolled-up totals, on the schedule you set.
Delivery manifestDocuments1,240Tracts1,318Flagged for review12FormatsPDF · DXF · SHP
Chaos in, standardized out.
A processing front carries your spec across the wall, converting each scan to a uniform output and rolling the totals into a manifest, flagged-for-review count included.
What we take in, and what comes back
- Recorded deeds
- Plats and subdivision maps
- Easement and right-of-way descriptions
- Legal descriptions in text form
- [additional document types per engagement]
- PDF, including scanned images
- Common image formats
- Plain text descriptions
- [bulk transfer method per engagement]
- PDF exhibits
- DXF for CAD
- SHP and GeoJSON for GIS
- KML
- Delivery manifest with rolled-up totals
How BPS works
What is the pilot scope?
We process a sample batch against your spec and review it with you. You set the acceptance criteria before we build to the full backlog.
How long does an engagement take?
Timelines depend on volume and spec. The pilot is scoped first, then the batch schedule is set with you. [placeholder: typical timelines]
Can the output be customized?
Yes. Formats, title blocks, naming, and coordinate system are built to your spec, so outputs land the way you defined them.
How is our data handled?
Documents are processed under our data handling and security practices. See the trust center for details. [placeholder: engagement-specific security terms]
Start with a pilot.
We plot a sample batch against your spec and review it with you before the backlog runs at volume.