Start free
Documentation
All documentation

Exchange

Read Exchange operations reports

Interpret turnaround, first-pass acceptance, vendor workload and backlog estimates, then inspect stored revision facts without overstating what they prove.

Updated

For
Workspace members coordinating vendors, reviews, and delivery
Typical time
5 minutes plus case review
Open operations reports

Before you start

  • Membership in the intended workspace with Exchange enabled
  • Recorded case history for historical measures; missing events remain missing

Procedure

Step by step

  1. Select the reporting period

    Open Exchange, then Reports. Choose the last 30, 90, or 180 days. Historical metrics use UTC dates and elapsed calendar days, including weekends. Current workload and assignments describe the present state rather than only cases created in that period.

  2. Read turnaround with its sample count

    Compare median time from case creation to first submission, vendor acceptance to first submission, first submission to its first review response, creation to first approval, and approval to first delivery. A sample belongs to the period when its ending milestone occurred. Missing or inconsistent dates are excluded, and a case counts at most once per measure.

  3. Separate first decisions from later approvals

    First-pass acceptance divides cases approved at their first review decision by cases with a first approval or request for changes in the period. Later resubmissions do not rewrite that first outcome. Submitted cases awaiting a decision and approvals with missing submission history are excluded from the rate. Read the count beside the percentage, especially for fewer than five decisions.

  4. Assess the current workload

    Review cases awaiting approval, including drafts, the observed first-approval pace, overdue cases, and the oldest open cases. The clearance estimate divides current case count by that daily approval pace. When work remains, fewer than three approvals means more history is needed.

  5. Open the case before making a decision

    Use current vendor assignments and case context to identify the next action. For a returned file, choose different Base revision and Candidate revision values in the case comparison, then Compare. Inspect the available facts and evidence alongside the source and returned document before approving an exact revision.

The workload estimate is conditional

The estimate assumes no new cases, unchanged capacity, and equal effort per case. It does not model page count, document complexity, staff availability, or future arrivals. It is a planning estimate, not a due date or service commitment. A workspace with no current work has no remaining backlog to clear.

Overdue status uses the current vendor milestone or, during submission and QA, the QA milestone, falling back to the overall due date. Review the actual case deadlines and dependencies before committing to a schedule.

Vendor rows describe assignments

Vendor workload groups current, non-revoked assignments by email. A case assigned to more than one vendor appears in every applicable row. Do not add vendor rows to obtain a workspace total, or read a shared case’s outcome as individual performance attribution.

First-pass acceptance measures the recorded review outcome. Neither an acceptance rate nor a short turnaround establishes accessibility quality or conformance.

Read revision facts within their limits

The comparison reports file identity, byte-size differences, page count, available PDF title and language, declared tagging, structure-tree and bookmark presence, and historical evidence attachments. Page facts include dimensions, rotation, and counts of annotations, links, and form controls for the first 200 pages. Longer files show a truncation notice.

Unavailable PDF facts remain unavailable; file identity and stored evidence can still be compared. Unchanged available page facts do not establish unchanged wording, appearance, reading order, or accessibility. This is not a text diff or pixel comparison. Review the source, returned revision, and acceptance evidence separately.

No samples is different from zero days

An empty measure may mean no qualifying ending milestone occurred in the chosen period, or required history is unavailable. Try another reporting period and inspect the case timeline. The report does not invent historical dates, infer an approval, or turn missing evidence into a pass.

Related guides