Receiving a PDF Portfolio: How to Inventory the Documents Inside

A file ending in .pdf may contain a PDF Portfolio rather than a single sequence of merged pages. That matters during intake: looking at a cover or preview does not mean you have examined every document inside. A complete review begins with an inventory of the components and their individual roles.

For a small team, the aim is simple. Make it possible for another reviewer to see what arrived, what was opened, what remained inaccessible, and which component supports each conclusion.

Distinguish the container from merged pages

Adobe describes a PDF Portfolio as a collection of component files that retain their own identities. Those components can include formats other than PDF. Adobe Portfolio overview.

A merged PDF, by contrast, is usually reviewed as one sequence of pages. Do not assume that a Portfolio's cover-page count represents the number of documents or pages available inside it.

Preserve the received container unchanged. Record its filename, arrival channel, and internal reference. The incoming PDF workflow still applies, but the unit of review now includes both the container and each relevant component.

Open it in a suitable viewer

If the browser displays only a message or cover, try the received file in an approved application that supports Portfolios. Adobe specifically directs users to Acrobat or Reader for viewing Portfolio contents. Adobe’s viewing guidance.

Do not conclude that the file is empty because one preview cannot expose its components. Equally, do not treat a successful preview as evidence that every component has been checked.

Follow your organization's normal precautions for unfamiliar attachments and embedded content. If a component requires an application you do not have or is outside the permitted review scope, mark it as not reviewed and arrange the appropriate handoff.

Create a component inventory

Assign each component a stable local reference linked to the container, for example P-006-A and P-006-B. Record the displayed filename, format, folder location inside the Portfolio if relevant, and intended role.

Add columns for whether the item opened, whether it was fully reviewed, and which issue remains unresolved. Do not infer chronology from the order in which the viewer happens to list components.

Use a batch review log if there are several files. One container-level “complete” status should not hide two components that nobody has examined.

Identify the intended relationships

Look for a contents note or sender explanation. Which file is the main document? Which is an appendix, translation, supporting record, or earlier version? If the relationship is unclear, ask the sender before treating all components as equally current.

A Portfolio may contain two similarly named proposals. Compare their stated revisions and ask which one governs the task. Keep both in the inventory even if one is later confirmed as superseded.

For source-and-translation pairs, follow the translated-document checklist. For a main document and appendix, map the references between them. Packaging them together does not automatically establish that they belong to the same version.

Review components without rewriting the container

If your approved viewer lets you save a component for inspection, place that output in a working directory and preserve the received Portfolio. Record where the component came from and which operation produced the working file.

Inspect each relevant PDF using the method appropriate to its content. A scan needs a readable-page check; a form may need field inspection; a signed document may need a separate validation workflow. CleanPDF does not validate cryptographic signatures or establish the origin of a component.

A CleanPDF edit-trace check can inspect some modification and hidden-information traces in supported PDF files. Do not assume that checking a Portfolio container means all embedded components were analyzed. Record exactly which supported file you submitted and the limits of the result.

A fictional example: one package, three roles

A project coordinator receives a Portfolio containing a current schedule, an earlier schedule, and a spreadsheet of supporting quantities. The browser shows only the cover page. In a supported viewer, the coordinator inventories the three components and asks the sender to identify the intended schedule.

The sender confirms the current schedule and explains that the old version was included for comparison. The coordinator reviews the current PDF, records the old file as reference material, and assigns the spreadsheet to a colleague with the appropriate tool and scope.

The package is not marked fully reviewed until that colleague returns a result. This avoids the misleading conclusion that opening one PDF established the contents of the entire delivery.

Report coverage explicitly

Your handover should state the container reference, number of inventoried components, items reviewed, and items not reviewed. Use a review report for material findings and link each observation to a component and page or location.

A useful conclusion is “four components inventoried; two PDFs reviewed; spreadsheet review pending; previous version retained for reference.” That is much more actionable than a blanket statement that the Portfolio passed a PDF check.