---
type: WebPage
title: Document Job Tracking and Delivery Routing | Marqius
description: Follow a recurring run from the current data to the finished PDF.
  Agree where the result should go and what to review when a job needs
  attention.
resource: https://marqius.com/features/job-tracking-and-delivery/
tags:
  - marqius
  - features
status: stable
sources:
  - id: official-page
    resource: https://marqius.com/features/job-tracking-and-delivery/
generated:
  by: process:marqius-site-build
  at: 2026-11-20T10:17:10.036Z
x_marqius:
  language: en
  source_sha256: 7e302041ee65998b5bbceaa76d4104bc723b18d3af35b1bf595e430c02e37bab
  extraction: public-main-content
---

WORKFLOW HANDOFF

# Track jobs and route completed files

Follow a recurring run from the current data to the finished PDF. Agree where the result should go and what to review when a job needs attention.

[Discuss Your Workflow](https://marqius.com/contact)[See Industry Examples](https://marqius.com/features/job-tracking-and-delivery/#industry-examples)

ILLUSTRATIVE CONCEPT

HOW IT WORKS

## What this changes in your workflow

A generated PDF is only useful when the right person has the right version. Agree which jobs need review, how staff retrieve the result and where the finished file should go.

[Explore Marqius Relay](https://marqius.com/relay/)

-   Review jobs as they progress through generation.
-   Retrieve completed files or inspect a job that needs attention.
-   Set the destination that will receive the finished files.

BUSINESS BENEFITS

## What it means for your operation

1.  ### Reduce time spent locating finished files
    
    Use job status and the agreed destination so staff know where the latest completed file belongs and can match it to the run.
    
2.  ### Resolve handoff problems sooner
    
    Give jobs that need attention a review path, an owner and a way to identify the affected edition. Staff can focus on the specific job before recreating output.
    
3.  ### Measure the handoff gap
    
    Track the time from completed generation to arrival at the agreed destination. Record missed deliveries, misrouted editions and manual follow-ups.
    

ILLUSTRATIVE SCENARIOS

## How industries can use it

Logistics & operations

### Keep depot reports separate

Tag the job with its depot and reporting date, then use the agreed destination for completed runs.

**In the proof:** Review an interrupted job and a completed one. Confirm where each appears and who is expected to act.

[Explore logistics & operations](https://marqius.com/industries/logistics/)

Retail

### Send the right edition to the right region

Keep a region reference through generation and route the approved price lists to the corresponding destination.

**In the proof:** Check editions with similar names and verify that their contents and destination agree.

[Explore retail](https://marqius.com/industries/retail/)

Financial services & insurance

### Separate preparation from release

Review representative statements and agree who retrieves or approves the completed output before the next handoff.

**In the proof:** Use synthetic records to check how the team handles a job that needs attention.

[Explore financial services & insurance](https://marqius.com/industries/financial-services/)

FIRST-PROOF CHECKLIST

## Test it on a document you already print

Start with an anonymised example and record what the finished file must do before the job moves to the next stage.

1.  **Define the job reference.** Choose a reference staff can match to the document, period and destination.
2.  **Walk through the main outcomes.** Test a completed run and a job that needs attention. Agree who checks each and when.
3.  **Verify the handoff.** Open the file at the intended destination and confirm its edition, contents and job reference.

EXPLORE NEXT

## Related workflow guides

-   [Personalised PDF batches](https://marqius.com/use-cases/batch-pdfs/)
-   [Personalised customer letters](https://marqius.com/use-cases/customer-letters/)

MARQIUS FEATURES

## Related capabilities

[All features](https://marqius.com/features/)

REUSABLE DESIGN

### Keep the layout your team approved

Reuse approved layouts and shared sections as names, figures, product details and other source information change.

[Explore feature](https://marqius.com/features/reusable-document-templates/)

VARIABLE DATA

### Personalise the next set of PDFs

Use one approved layout and a fresh set of records to prepare statements, correspondence and other documents that vary from recipient to recipient.

[Explore feature](https://marqius.com/features/variable-data-personalisation/)

RELIABILITY

### Catch issues before the handoff

Use press checks and page-level findings to review the file before release. Strict mode can stop a run when a check raises a warning, so the next step starts with a decision.

[Explore feature](https://marqius.com/features/press-checks-and-reliability/)

## Bring a document your team already makes.

Tell us how it’s produced today and what you need from the next run. We’ll discuss a representative proof.

[Discuss a Sample](https://marqius.com/contact)

QUESTIONS & ANSWERS

## Document Job Tracking and Delivery Routing: frequently asked questions

### What should we test with a receiving system?

Verify where a completed file lands and how the receiving team identifies its job or edition. Confirm the exact handoff during evaluation.

### What should happen when a job needs attention?

Agree who reviews the job, where they find the relevant output or details, and what they check before release.

### Can we check the route without using customer records?

Yes. Use a synthetic batch with the same naming and destination rules before testing with live records.

Source for this page [^official-page].

[^official-page]: https://marqius.com/features/job-tracking-and-delivery/

[Browse this section](index.md) · [Knowledge index](../index.md)
