FAQ

FAQ

Is this a native Xactimate writer?

No. The project generates a deterministic ESX-style package and readable XML output, but it does not claim to be a proprietary native XACTDOC.ZIPXML writer.

For the exact assumptions, read:

• ESX mapping notes
• XML/ESX assumptions

Does it support scanned PDFs?

Yes, on a best-effort basis. The app can apply local OCR when pages appear scan-heavy or text-poor. Results still depend on scan quality and layout clarity.

Is docs_repo the source of truth?

Yes. The wiki is the fast surface layer. docs_repo/ in the main repository is the deeper technical source of truth.

Can I add support for new estimate layouts?

Yes. That is one of the highest-value contribution areas.

Start here:

• How to add new parsers
• PDF field mapping

Does the app work without Python?

It can, if you are using a packaged Windows build from a release artifact. If no packaged release asset is available, you will need to run from source or build the executable locally.

Where should bugs be reported?

Use the repository issue templates:

• Open issues
• Support guidance
• Security reporting

How do I tell whether the problem is parsing or export?

Check the generated *.canonical.json first.

• if the canonical file is already wrong, the problem is usually in ingestion or parsing
• if the canonical file looks right but the XML/package looks wrong, the problem is usually in mapping or export

Is this only for roof estimates?

No. Roof-related measurements are an important supported field family, but the project is broader than roofing-only use cases.

Is this ready for every carrier and every estimate layout?

No. The app is real and usable today, but layout coverage is still evolving and should not be overstated.