Processing and activity
Whether you scan pages or use a watched folder, Paperweight keeps protected copies of the originals and the settings for that job. It checks the input, applies the selected output profile, checks the result, and delivers the file to its destination.
Normalization and validation
Paperweight preserves grayscale and black-and-white values where possible. TIFF output uses Group 4 compression for wholly black-and-white batches and ZIP otherwise. When rebuilding PDF pages as images is unsuitable, Paperweight can optimize the existing PDF structure. Already-efficient files may pass through unchanged if they meet your selected settings.
Output is reopened and checked for format, byte limits, page count, dimensions, codecs, and supported restrictions. Appearance/pixel comparisons guard transformations. Have the staff who use the documents compare sample output with the originals for readability and completeness; automated checks cannot judge which details matter to their work.
Read Activity
Activity exposes job status, error code, original/result bytes, page count, and timing. Stored operational details also include acquisition, profile/revision, destination ID, configuration revision, processing decision, and a stable installation ID. The visible table is local to the signed-in user's job store.
| State | Meaning |
|---|---|
| Acquiring | Originals are being captured or snapshotted |
| Queued / Processing | Ready for the worker / worker running |
| Validated | Output passed checks; publication remains |
| Publishing | Publication intent recorded; filesystem handoff in progress |
| Published | Final file handoff recorded; source cleanup/archive may remain |
| Archived | Successful cleanup completed; local recovery material retained |
| Held | Review required before further action |
| Uncertain | Delivery cannot be established safely; downstream reconciliation required |
| Expired | Eligible recorded archive artifacts were removed |
Measure efficiency carefully
Per-job reduction is 100 × (1 - resultBytes / originalBytes) when original bytes are positive. Negative values mean output grew. Compare similar input types and profiles; scanner PNG masters and direct folder imports have different baselines. No fixed savings percentage applies to every document.
The goal is to fit the same document workload into less disk space, without reducing how much your team captures. A preliminary trial in a clinical environment measured up to 90% less disk space consumed by filed documents normalized with Paperweight automations compared with documents captured directly with Canon scanning software. Savings vary by document and settings; review output quality as well as file size.
Team reporting
Activity and efficiency figures are currently available on each workstation. Cross-team reporting and trends are planned; this version does not include a fleet dashboard, reporting API, or automated trend exports.
Operational history excludes source filenames/paths and document content, but can include Windows account identities associated with capture and processing. File ownership or inferred writer information does not establish who scanned a document. Protect this account information according to your organization's policies. Recovery records also contain paths needed for cleanup; do not upload raw job data to public tools.