FAQ
This page answers common practical questions about AXIS and EPM in plain language. Read the Glossary first, then use this page for quick workflow questions.
AXIS
Why is AXIS needed?
Appraisal data often sits in software-specific formats that do not move cleanly between systems. AXIS is meant to define shared Appraisal Report (AR) and Appraisal Review (APR) data meaning and structure so exchange is more consistent.
In practical terms, AXIS gives producers and consumers a common contract they can implement without being locked to one vendor format.
Does AXIS replace the PDF?
No. AXIS does not replace the PDF as a presentation document. It hitches a ride with the PDF inside an EPM envelope object.
AXIS defines structured data. EPM is the envelope pattern commonly used to carry that data with a PDF.
Does including AXIS data alter the printing or viewing of my PDF?
No. The report will look and print the same.
Structured data is added for machine use and does not need to change how the document is visually presented.
Is AXIS limited to PDFs?
No. AXIS is not tied to one transport format.
PDF is a common delivery path, but AXIS data can be exchanged in other ways when workflows require it.
How do I get AXIS data in my AR or APR workflow?
Most implementations generate structured AXIS data from the same source data used to create a PDF report.
If the delivery target is PDF, the AXIS payload is typically carried in an EPM manifest embedded in that PDF.
Why do I need AXIS data?
Reliable structured data improves interoperability, validation, analytics, and reuse.
It also reduces fragile extraction workflows and supports downstream BI and AI use where appropriate.
The data is transferred in a PDF. Why not use that data?
You can extract text from a PDF, but it is often brittle across layouts and software outputs. AXIS data (structured data) is typically placed inside a PDF. It contains the same data used by appraisal software when generating a PDF but in a machine-readable form. This data does not impact the formatting or output of the document. The AXIS object increases the quality of the data that would otherwise have to be scraped or extracted from the PDF.
AXIS data is structured by design, so consumers can parse semantics directly instead of inferring it from visual layout.
Is AXIS USPAP or other standards compliant?
AXIS is a data standard, not an appraisal analysis engine.
Professional compliance obligations remain with the appraiser and the systems used to produce the final work product.
Is AXIS AO-41 Compliant?
Similar to USPAP questions, AXIS carries structured data and does not perform appraisal analysis by itself.
What AXIS can do is improve data quality and reuse for tools built on top of that data.
Is AXIS data secure?
AXIS defines data structure and meaning; encryption decisions are implementation choices.
When AXIS data is carried in EPM, producers can declare payload compression and encryption details in the EPM object.
See also: EPM Payload Encryption and Compression
Is EPM required to use AXIS?
No. EPM is not required to create or transfer AXIS data.
EPM is recommended in many workflows because it supports consistent payload packaging and optional payload compression/encryption details.
I have heard of other data standards. Why not use one of those?
AXIS and EPM are designed for flexibility, open standard collaboration, and broad implementation.
Different standards have different governance and access models. For example, MISMO and RESO each serve important roles in their own domains.
In some cases, standards become bloated and drift over time due to their design. This site focuses on AXIS and EPM because they align with a transparent, extensible, interoperability-first direction for this project.
I have seen structured data transmitted in a separate file. Why not use that method?
This type of data delivery is common in the residential appraisal domain for federally related transactions.
EPM reduces dependency on sidecar file delivery and helps keep presentation and machine-readable data together in one transport package.
See also: Why the PDF Is the Right Home for Structured Appraisal Data
EPM
What is EPM?
EPM (Embedded Payload Manifest) is an envelope object for carrying one structured payload.
Like a mailing envelope, it carries content plus metadata that helps consumers identify and process what is inside.
Why is EPM needed?
EPM solves a different problem than AXIS.
AXIS defines appraisal data semantics. EPM packages a payload so it can travel with a host document in a predictable way, with optional payload compression and encryption metadata.
See also: EPM Payload Encryption and Compression
Is EPM only needed for AXIS?
No. EPM is payload agnostic and can carry many payload types, not only AXIS.
AXIS plus EPM is one important use case in this site, but EPM itself is broader.
General Questions
Where should I start if I am new to this topic?
Start with the Glossary, then read AXIS Overview and EPM Overview.
The glossary is where core terms are defined so the rest of the site can stay plain language and concise.