PrecisionDocs

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:

  1. Click New Project in the sidebar.
  2. 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.
  3. Review the site size and confirm the project details.
  4. Enter the project details such as project name, municipality, and client context.
  5. (Optional) Click Verify next to each ordinance URL field to preview the source the platform will index. The verifier classifies the URL, counts chapters, and rejects non-municipal entities (sanitary districts, school districts, park districts) before you spend bootstrap time on a wrong source.
  6. (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.
  7. 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
  • Use the Verify button on ordinance URL inputs whenever you are pasting a custom source — it catches sanitary-district / school-district URLs that look right but are not municipal
  • 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 pricing and access work?

PrecisionDocs bills through a shared workspace credit wallet. Your organization buys credits, and everyone in the workspace draws on the same balance.

How access works:

  • Credits belong to the organization, not to one individual user.
  • Any active member of the workspace can use the shared credit pool. There are no per-user licenses to assign.
  • Owners buy credits, set auto-refill, and manage the payment method in Account -> Billing.
  • Owners manage who is in the workspace, and who has access to the shared credits, in Account -> Organization.

What credits buy:

There is no per-feature gating. Every workspace gets the full product - project chat, government data lookups, ordinance research, document upload and search, maps, reports, and collaboration. Credits pay for the AI work those features run, and larger credit packages include bonus credits.

Pilot is a one-shot evaluation and does not auto-renew. To continue after Pilot, an owner explicitly buys a credit package from the app or works with support.

See Credits & Usage in this help center for what spends credits and why amounts vary. For quote terms or procurement questions, contact info@precisiondocs.ai.

Where do I see my credit balance and usage?

Your balance is on the wallet readout in the app, and the detail lives in Account -> Billing and Account -> Usage. There is no project quota pill.

Account -> Billing shows the workspace credit balance, credits used in the selected period, auto-refill settings, payment method, and invoices for credit purchases.

Account -> Usage shows what those credits were spent on, with Recent, Projects, and Users views so you can trace spend to a site or a teammate.

The balance is workspace-wide, so every member sees the same number rather than a personal allowance.

Legacy workspaces still on a per-user license subscription instead see their assigned tier, included usage value, and remaining value on the Billing tab.

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:

  1. Create the project and verify parcel selection. Make sure acreage, municipality, and site name are correct. Use the Verify button on ordinance URLs if the auto-discovered source looks wrong.
  2. Wait for bootstrap to finish both municipality and county. The chat-readiness gate now waits for both pipelines — the bootstrap dial holds at 70% while county is still indexing even if municipality is done. Do not judge ordinance answers while either is still queued.
  3. 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.
  4. Upload only the key source documents next. Typical starter set: survey, geotech, Phase I ESA, zoning letter, concept plan.
  5. 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.
  6. Validate the critical blockers one by one. Flood, wetlands, ordinance constraints, access (frontage + ROW), environmental, and geotechnical issues should each be checked directly.
  7. 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.

Other help topics