Multi-page documents are not one proof. They are many proofs in one document.
Aproove treats every page inside a multi-page document as its own reviewable component. Reviewers approve, reject, or mark up each page independently. Workflow actions fire per page, not per document. When a revised version comes back, Aproove's Smart Scan compares every page to its prior version and only re-versions the pages that actually changed. Reviewers verify only what moved, not the whole document for a focused document review and approval process.
What it is
Page-Level Smart Review is the configurable Aproove behavior that treats every page inside a multi-page document as its own reviewable proof. A 300-page document is, from the reviewer's perspective, 300 independent decisions. Approval can fire on a per-page basis. Workflow actions can be conditioned on per-page status. A revised version can re-version only the pages that actually changed.
The capability in our document version control software has two related mechanisms:
- Page-level decisions. Each page within a multi-page document carries its own status: approved, rejected, marked up, no status. Reviewers act per page. The workflow responds per page.
- Smart Scan versioning. When a new version of a multi-page document is uploaded, Aproove's processing engine compares each page against the prior version. Pages that actually changed get a new version number. Pages that did not change retain their previous version number. The same document can carry different version numbers across its pages.
A "Changed" status filter in Project Plan View lets reviewers see only the pages that moved between versions, so the entire document does not need to be re-read every cycle.
Why it matters
Most document version control software options treat a multi-page document as a single proof with a single decision. A reviewer with a 50-page document and three pages that need revision has two options: reject the whole document (blocking the 47 pages that are fine) or approve the whole document (releasing the three pages that have issues). Neither is right. The platform forces the reviewer to lie about what they actually decided.
The common workaround is to split the document into single pages before upload, which produces a different set of problems. The reviewer gets 50 separate proofs in their queue, 50 separate email notifications, and 50 separate decisions to track. The production team manually collates comments from 50 proofs back into the original document. The investment in proofing software starts producing more work, not less.
Aproove's page-level model solves both problems at once. The document stays whole. The reviewer gets one document in their queue. But each page acts as its own proof for the purposes of decisions, status, notifications, and versioning. The document is one thing for storage and navigation, many things for review.
For regulated content, the second mechanism matters even more. When a new version arrives, Smart Scan flags every page that changed (expected change) and also flags pages that changed that should not have (unauthorized change). A reviewer comparing version 12 to version 11 sees not just "page 14 was updated as requested" but also "page 7 changed, and nobody asked for that." Compliance teams catch unintended drift before it reaches production.
How it works
Upload. A multi-page document (PDF, multi-page TIFF, multi-page Office file, or any of the 180+ supported multi-page formats) is uploaded as one file. Aproove's processing engine breaks the document into per-page components at processing time, generating a preview and a reviewable surface for each page.
Review. In the Review Interface, reviewers navigate the document page by page. The Flatplan view shows every page with its current status indicated by a colored border (green for approved, red for rejected, orange for annotated, grey for no status, blue for "changed"). Reviewers can act on a single page or select multiple pages and apply a status across the selection.
Workflow integration. Workflow actions can be configured to respond per page. A page marked approved can fire its own routing decision while the rest of the document continues in its current step. Notifications can fire per page or per document, configurable per workflow.
Smart Scan on new versions. When a new version of the document is uploaded, the Smart Scan processes every page against its prior version. Pages with detected differences get a new version number; unchanged pages retain their previous version. The Flatplan shows version numbers per page, so the reviewer can see at a glance which pages need re-review.
The "Changed" filter. A "Changed" status in the Flatplan filters the view to only the pages flagged as different from the previous version. Reviewers move directly to the work inside the document version control software that needs them.
Benefits
- One decision per page, not one decision per document. Reviewers express what they actually decided, page by page, without rejecting good pages to flag bad ones or approving bad pages to release good ones.
- The document stays whole. No splitting into single-page files. No 50 separate proofs cluttering queues. One file, navigated as a document, reviewed per page.
- Re-review only what changed. Smart Scan re-versions only the pages that actually moved. Reviewers verify the changed pages and trust the unchanged pages, instead of re-reading the entire document every cycle.
- Unauthorized changes are flagged. Pages that changed when they should not have are highlighted alongside expected changes. Compliance teams catch drift before it ships.
- Notifications fire on real activity. Per-page status changes generate per-page notifications, so the noise floor matches the work that actually happened, not the size of the document.
- The Flatplan tells the whole story at a glance. Status colors per page, version numbers per page, "Changed" filter on demand. The state of a 300-page document is visible in one view.
Who it's for
- Regulated industries with long multi-page documents. Pharma, healthcare, financial services, Medicare and Medicaid marketing, where 100-page-plus documents are routine and partial-document edits are the norm.
- Catalog and direct mail production teams managing high-page-count assets where most pages stay stable across versions.
- Brand and creative governance teams validating that revisions did not introduce unintended changes elsewhere in the document.
- Compliance and audit teams who need defensible records of which pages changed, when, and who approved them.
- Operations leaders evaluating proofing tools against the question "does this handle our actual document sizes, or do we have to break files apart to work with it?"
Under the hood
Page-Level Smart Review is configurable per project schema. When enabled, Aproove's Processing Agent decomposes multi-page documents into per-page components at ingest, with each page treated as a reviewable proof within the parent document container. Decision state, version history, and audit trail are maintained per page. The Smart Scan engine compares each page in a new version against its prior version using content-aware diff at the page level; pages with detected differences receive incremented version numbers, while unchanged pages retain their previous version. Workflow actions can be conditioned on per-page status (approved, rejected, annotated, changed) and fire independently per page. The Flatplan view aggregates per-page status and version into a single visual representation, with filter support including a "Changed" status that surfaces only pages with differences from the prior version. The audit trail captures decisions and version events at the page level alongside document-level events.
Built for regulated environments where failures create real risk
Insurance, healthcare, and enterprise teams face unique approval challenges. Aproove handles state-by-state variations, mandated language, FDA submissions, and multi-geography brand governance without breaking a sweat.
Trusted by leaders
Used by teams that cannot afford uncertainty in their approval process.
"Implementing Aproove has dramatically reduced errors, increased motivation and satisfaction across the teams and importantly, saved the operation significant hard costs."
“The Aproove team are the best team in the world. I feel like I'm their only customer, they are always there for me.”
"Within a short period, we were able to reduce 25 workflows into a single workflow. The team saw a 15-week reduction in getting new marketing packages from idea to market. More importantly, it ensured that all the packages were compliant with regulatory requirements. All steps, comments, and approval are captured and saved for any audits."
More ways to streamline high-stakes workflows
See how Aproove turns a 300-page document into 300 independent decisions
