The archive asks for PDF/A-2b. Start by checking the version of site-record.pdf you plan to deliver. In Ulet, open Page → PDF/A and review the preflight findings for that profile.

Follow the finding back to the export

If the report flags an output intent, check the archive export settings in the tool that produced the PDF. Re-export to a separate file such as site-record-archive.pdf. Reopen it and compare the map and its legend with the original. Run the preflight again on the new file.

An example preflight flags the output intent for investigation.

Illustrated preflight finding. Write down the exact profile and file checked.

Validate the actual file you will archive

Run a full validator such as veraPDF against the required profile on site-record-archive.pdf. Save the report beside that specific file. A clear preflight means the preliminary checks found no issue within their scope. If a correction creates a new PDF, run validation again on the replacement.

The final archive file is paired with its own veraPDF validation report.

Illustrated archive record. Validate again after any edit or re-export.

veraPDF validation profiles and rules