PrecisionDocs

Troubleshooting — Help Center

The fastest fixes for access, ordinance, report, and answer-quality problems.

Why is a teammate blocked from AI work?

Two things gate AI work: the member must be active in the workspace, and the workspace credit wallet must have available credits.

Owner checklist:

  1. Open Account -> Organization and confirm the person appears as active on the Access roster. Re-activate them if they were suspended.
  2. Confirm they accepted the org invite and signed in with the invited email.
  3. Open Account -> Billing and check the credit balance. If the wallet is empty, add credits or turn on auto-refill.
  4. If the block came from a connector rather than the app, check whether that API key carries a daily or monthly credit cap.
  5. If a credit purchase should have landed but has not, check whether Stripe is still waiting on payment confirmation.

Suspended or removed members stay in the member history but cannot spend credits until an owner reactivates them.

If your workspace is on the older subscription model, one more gate applies - see We are on an older per-seat subscription in Credits & Billing.

Why can't the agent find my ordinance answer?

Most ordinance misses come from one of these causes:

  • Bootstrap is not complete yet (check both muni AND county)
  • The question is too broad
  • The answer lives in an overlay, special district, or cross-reference you did not name
  • The indexed source belongs to a same-name municipality in a different county
  • The relevant chapter was never present in the source code set
  • The relevant rule lives in a separate zoning ordinance, subdivision code, stormwater manual, design standard, or PDF

Fix sequence:

  1. Confirm bootstrap status is complete on both pipelines.
  2. Ask a narrower question tied to one topic like setbacks, parking, stormwater, or landscaping.
  3. Ask the agent to identify the exact chapter or section first, then summarize it.
  4. If the answer likely lives in a separate code product, add it as a supplemental ordinance source or ask the agent to find and index it.
  5. If the source appears to be the wrong municipality or county, open that scope on the Project Home ordinance sources card and use Edit sources to add the correct code, and email info@precisiondocs.ai with the right municipality, county, and state to have the wrong source corrected.
  6. If needed, cross-check with web search or uploaded jurisdictional correspondence.

Good prompt: Find the exact ordinance sections for parking counts and reduction options for this site. If those rules are in a separate zoning or land-development code, find that source first.

What should I do if report generation fails?

Report generation is a multi-step workflow, so the best recovery path is to verify the inputs before retrying.

Use this recovery SOP:

  1. Confirm the project has completed bootstrap on both muni AND county.
  2. Check that the critical evidence exists: ordinance context, flood, wetlands, soils, and any uploaded consultant documents you expect to be cited.
  3. Ask the agent to summarize the major constraints in chat first. If that answer is weak, the report will also be weak.
  4. Retry report generation only after the source issues are resolved.

If a report fails repeatedly on one project, reduce ambiguity first by asking for the exact section outputs you care about in chat.

What should I do if the agent gives an incorrect or incomplete answer?

Use a source-first correction workflow.

  1. Identify what appears wrong: missing citation, wrong document, wrong parcel, stale ordinance, or unsupported conclusion.
  2. Ask the agent to answer again using only the correct source set.
  3. If necessary, open the cited source and compare the claim manually.
  4. For elevation or surveyed conditions, prefer your authoritative project documents over generalized public datasets.
  5. If a fact is repeatedly wrong, correct it in chat directly: That zoning is actually R-2 - verify against the ordinance. If you own the project and the ordinance confirms it, the agent records the correction so subsequent reports use it; if you do not own the project, ask the owner to make it.
  6. If the missing source is external, add or ingest the source first, then ask the agent to re-answer from that evidence.

Best correction prompt:

That looks wrong. Re-answer using only the uploaded survey and the cited FEMA source, and show the exact evidence.

When the answer affects engineering judgment, permitting, or client communication, always validate before treating it as final.

Continue reading

Other help topics