EPM Overview
EPM is an open standard for packaging machine-readable payload content in a structured manifest, usually embedded in a PDF host document.
EPM is payload agnostic: it can carry different payload types, not just one domain model. That flexibility makes EPM a strong transport pattern across industries, and a particularly good fit for AXIS workflows.
AXIS and EPM are complementary:
- AXIS defines data meaning and document definition contracts.
- EPM defines packaging, discovery, and processing behavior for exchange.
In this site context, that includes both Appraisal Report (AR) and Appraisal Review (APR) workflows.
With this model, both producer and consumer know the same exchange expectations through explicit contracts.
In practice, this supports one-file delivery: the PDF remains the human-readable document, while the embedded manifest carries structured content for system processing.
For a plain-language explanation of why this embedding model was chosen, see Why the PDF Is the Right Home for Structured Appraisal Data.
For consumers, EPM supports fast candidate discovery through discovery fields and then checking each payload on its own. Invalid candidates can be rejected without blocking valid payloads in the same host document.
EPM also supports payload-layer security and optimization:
- Encryption is applied at the payload/application layer, not by encrypting the PDF container.
- Compression is applied to payload content and declared in metadata/profile rules so consumers can decode deterministically.
For a deeper look at payload-layer protection and optimization, see EPM Payload Encryption and Compression.
Current guidance is PDF-first, with PDF/A-3 minimum profile support and PDF/A-4f support where requirements are met. Under PDF/A, PDF container encryption is not permitted; payload encryption remains available at the application layer.
Like AXIS, EPM is being developed through open collaboration with open source schema artifacts. That gives vendors and implementers a practical path to adopt, contribute, and compete on software quality and implementation outcomes rather than on closed exchange formats.
This page is an orientation summary. For full normative requirements and implementation details, see epmstandard.org.