Getting Started — Help Center
Project setup, onboarding, and the fastest path to a useful first analysis.
What is PrecisionDocs?
PrecisionDocs is a chat-first due-diligence workspace for civil engineering teams.
A project combines your parcels, municipal context, uploaded documents, maps, and report outputs in one place so the agent can answer project-specific questions instead of giving generic AI answers.
Use it when you need to:
- Screen a site quickly before spending time on manual research
- Pull together flood, soils, wetlands, elevation, seismic, road frontage, and ordinance findings into one thread
- Search uploaded reports, plans, exhibits, and images with citations
- Generate exportable maps and Due Diligence reports
The product is designed to support engineering judgment, not replace it. Treat it as an acceleration layer with source-linked outputs.
How do I create my first project?
Use this standard workflow:
- Click New Project in the sidebar.
- Search the address and select the parcel or parcels that define the site. If your project starts from a boundary file, use the boundary-file import when available and upload a zipped shapefile, KML/KMZ, or GeoJSON so the wizard can resolve the matching parcels from the geometry.
- Review the site size and confirm the project details.
- Enter the project details such as project name, municipality, and client context.
- (Optional) Paste an ordinance URL if the auto-discovered source looks wrong. The wizard checks it as soon as it is pasted and shows the result under the field - read that result and do what it says. Pasting a URL counts as choosing it, so confirm yourself that it is the right municipality and the right slot, and the governing code rather than another entity's, before you continue. For what the wizard does with a URL you paste, see What happens when I paste an ordinance URL into the project wizard?
- (Optional) Add separate supplemental code sources, such as a zoning ordinance, land-development code, subdivision regulations, or stormwater manual. These are reference sources, not a replacement for the governing ordinance unless the wizard explicitly says the governing source is missing.
- Finish creation and let the bootstrap process index ordinance data for the municipality and county in parallel.
Best practice for first setup:
- Confirm you selected the correct parcel geometry before moving on
- Use a boundary file when the address search returns too many candidates, the site is assembled from partial parcels, or the APN is not reliable
- Use the municipality that matches the governing ordinance, not just the mailing address
- Read the result under any custom ordinance URL you paste, then confirm the municipality, the slot, and that the source is the governing code at all - a URL you paste is treated as your choice, so the wizard does not reliably catch any of those mistakes
- Add supplemental sources for separate zoning, subdivision, land-development, stormwater, design-manual, or overlay code products before project creation when you already know them
- Ask the agent for a baseline summary immediately after bootstrap finishes so you can verify the project context is correct
How does access and billing work?
PrecisionDocs bills through a shared workspace credit wallet. Your organization buys credits, and everyone in the workspace draws on the same balance.
Access
- Credits belong to the organization, not to one individual. There are no individual seats to assign.
- Any active member of the workspace can use the shared credit pool.
- Owners buy credits, set auto-refill, and manage the payment method in Account -> Billing.
- Owners manage who is in the workspace in Account -> Organization.
What credits buy
Every workspace gets the whole product - project chat, government data lookups, ordinance research, document upload and search, maps, reports, and collaboration. There is no per-feature gating. Credits pay for the AI work those features run.
Where to see your balance
The wallet readout in the app shows the current balance. Account -> Billing has the balance, credits used in the period, auto-refill, payment method, and invoices. Account -> Usage shows what the credits were spent on, with Recent and Projects views, plus a Users view for workspace owners.
Pilot is a one-shot evaluation and does not renew automatically. To continue after it, an owner buys a credit package.
See Credits & Billing for what spends credits, why amounts vary, and how to buy more. For quote terms or procurement, contact info@precisiondocs.ai.
What is the best SOP for a brand-new project?
Use this sequence if you want the cleanest project history and the best first report output:
- Create the project and verify parcel selection. Make sure acreage, municipality, and site name are correct. If the auto-discovered ordinance source looks wrong, paste the correct URL and read the verification result under the field before you continue.
- Wait for bootstrap to finish both municipality and county. The chat-readiness gate waits for both pipelines - the bootstrap dial keeps moving through the high 80s and low 90s while the county is still indexing even if the municipality is done. Do not judge ordinance answers while either is still queued.
- Review the auto-generated Due Diligence + Feasibility Assessment. These are produced during bootstrap from available API data so you have a Tier-1 risk view before uploading anything.
- Upload only the key source documents next. Typical starter set: survey, geotech, Phase I ESA, zoning letter, concept plan.
- Use a guided workflow or ask for a baseline due-diligence summary in chat. Guided workflows are best when you want a checklist path; a direct summary prompt is fastest when you already know the question.
- Validate the critical blockers one by one. Flood, wetlands, ordinance constraints, access (frontage + ROW), environmental, and geotechnical issues should each be checked directly.
- Export maps, GIS layers, or reports only after source checks. Reports and polished exhibits are strongest when the underlying facts have already been checked in chat and on the map panels.
If anything looks wrong, fix the project inputs first - correct the zoning override, add a chat correction, or re-upload the right document - instead of trying to patch the narrative later.