# Route Delivery List

The Route Delivery List is a definitive list of subscribers on a particular route. It can be used in a variety of situations—for example, when a new carrier begins delivering a route. If a TM product is delivered with the publication (see Deliverable in the Setup Manual), occupants receiving the TM product may also be listed. Route Lists can be generated here; they can also be set up to print on bundle tops.

#### To produce the list:

* Select Route Delivery List from the Route menu to display the Route Delivery List Report window.<br>

  ![](https://1417315899-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1ToZXx8io0JJXNBRcPOt%2Fuploads%2FWCAqoGwzkZHlp51OkUlt%2FRoute%20Delivery%20List%20Report.png?alt=media\&token=2c479029-ccfe-482f-894f-8fea7f1a94c3)
* Click Add and complete the following fields.<br>

  <table><thead><tr><th width="167">Field</th><th width="116.41946010086025">Type</th><th width="374.2">What to enter</th></tr></thead><tbody><tr><td>PRODUCT</td><td>setup</td><td>Enter the publication for which to generate the delivery list.</td></tr><tr><td>REPORT DATE</td><td>date</td><td>Enter the date for which to generate the delivery list. If a past publishing date is entered, subscribers will be listed as of that date, but only “active” and “active or additional product” subscriber types can be entered in the next field. See the note about input files below.</td></tr><tr><td>INCLUDE PENDING</td><td>yes/no</td><td><p>Indicate whether pending (unprocessed) starts, stops, moves, and other subscriber transactions should be taken into account.</p><p></p><p>For example, if the Route Delivery List is being run for the future date of 8/7, and there is an unprocessed new start for 8/7, the subscriber will be listed if you select this checkbox.</p></td></tr><tr><td>SHOW BONUS DAY</td><td>yes/no</td><td><p>The report can include bonus day subscribers (subscribers that will receive the paper even if it is not a normal delivery day for them).</p><p></p><p>Enter yes if both bonus day and regular subscribers should appear, enter no if only regular subscribers should appear, and enter only if only bonus day subscribers should appear.</p></td></tr><tr><td>SUBSCRIBER TYPE</td><td>predefined</td><td><p>Enter the type subscriber that should appear on the delivery list. Choices are active subscribers, active or additional product, inactive subscribers, all subscribers, all households, and non-subscribers.</p><p><br>An inactive subscriber is a temporarily stopped subscriber.</p><p><br>A non-subscriber is an occupant with no subscription history.</p><p><br>If “active or additional product” is selected, occupants receiving a TM product being delivered with this publication will also be listed.</p><p><br>If “all households” is selected, Billing Method, Delivery Schedule, and Delivery Day are skipped.</p></td></tr><tr><td>REASSIGNED ROUTES</td><td>yes/no</td><td>Indicate whether to include subscribers whose subscription route is different from their address route (see <a href="../../route-service/setup/rerouting">Rerouting</a> for a discussion of subscription routes versus address routes).</td></tr><tr><td>INCLUDE ADDITIONAL PRODUCTS</td><td>yes/no</td><td><p>A TM product or another publication may be set up to print with this publication’s route list (see Deliverable in the Setup Manual).</p><p></p><p>In this case the route list would include both the subscribers for this publication and the TM addresses or subscribers for the other publication. Indicate whether additional products should be included in the route delivery list.</p></td></tr><tr><td>INCLUDE NON-DELIVERY DAYS</td><td>yes/no</td><td>Indicate whether you want to include a subscriber’s additional products that are not delivered on the selected report date.</td></tr><tr><td>ADDITIONAL PRODUCT</td><td>setup</td><td>TM products and other publications can be set up to “always” print with this publication, or to “ask”. If they are set to “ask”, you must enter the product in this field. Enter “*” to multi-select products.</td></tr><tr><td>PRINT ORDER</td><td>predefined</td><td>Indicate whether the report should be printed in order of address, carrier delivery sequence, or postal route.</td></tr><tr><td>BILLING METHOD</td><td>predefined</td><td>Specify the billing method to include in the report. Choices are office pay, carrier collect, paid complimentary, unpaid complimentary, or * (to multi-select billing methods).</td></tr><tr><td>PRINT RATE CODE</td><td>yes/no</td><td><p>Indicate whether rate codes should appear on the Route Delivery List for subscribers that have rates (i.e., office pay subscribers).</p><p>Because this is the subscriber’s current rate, this field is available only if running the report for a current or future publishing date.</p></td></tr><tr><td>DELIVERY SCHEDULE</td><td>setup</td><td>Specify the delivery schedule to include in the report or enter “*” to multi-select delivery schedules. You can leave this field blank if you want to run the report for a specific day.</td></tr><tr><td>DELIVERY DAY</td><td>predefined</td><td>If you left Delivery Schedule blank, specify the day of the week to cover in the report.</td></tr><tr><td>SELECTION TYPE</td><td>predefined</td><td>Indicate whether routes to be included in the report should be selected by area, region, zone, district, or route.</td></tr><tr><td>PRINT ALL</td><td>yes/no</td><td>Indicate whether all routes for the publication should be included in the report.</td></tr><tr><td>SELECTION</td><td>setup</td><td><p>If you entered “n” in Print All, specify the area, region, zone, district, or route to include in the report (based on what was entered in Selection Type).</p><p>Enter “*” to multi-select areas, regions or zones. In the case of districts and routes, there is no multi-select.</p><p>However, you can enter “*” or click the Find icon to the right of this field to add districts or routes one at a time in a separate maintenance window.</p></td></tr><tr><td>REPORT TYPE</td><td>predefined</td><td>Indicate whether a standard Delivery List or Throwoff List should print. The Throwoff List is a condensed version of the Delivery List, showing only the address, name, delivery schedule, number of copies and (optionally) delivery instructions for subscribers on a given route; it is only available when running the report for active subscribers.<br>You may also choose to Export the Route Delivery List in the standard format or a file-mapped format. If exporting, totals for the Route Delivery List will still be displayed in the window.</td></tr><tr><td>USE FILE MAP</td><td>yes/no</td><td>If exporting data, indicate if you are using a file map that has a usage of “RouteData”.</td></tr><tr><td>FILE FORMAT</td><td>setup</td><td><p>In FILE FORMAT, identify the file map you will use (must be set up in advance).</p><p>If you are interfacing route data to RouteSmart, select the “RouteSmart” format here.</p></td></tr><tr><td>EXPORT FILE</td><td>open (14)</td><td>If Report Type is “export”, enter the name of the ASCII file that should be created by the export. The format for the file is given in Appendix B.</td></tr><tr><td>SPACING</td><td>predefined</td><td>Indicate whether the spacing should be single or double.</td></tr><tr><td>PRINT DELIVERY INSTRUCTIONS</td><td>yes/no</td><td>Indicate whether to include delivery instructions in the report.</td></tr><tr><td>PRINT TRUCK</td><td>yes/no</td><td>Indicate whether to include the truck, truck name, and supplying truck ID in delivery list.</td></tr><tr><td>ADDITIONAL REPORTS BY ROUTE</td><td>yes/no</td><td><p>Indicate whether to create a separate file for each route, as well as the full route delivery list. If you select this checkbox, a separate file will be created for each route, with the product ID and route ID appended to the file name entered in View/Print.</p><p>If you do not select this checkbox, only the full route delivery list will be produced.</p></td></tr></tbody></table>
* Click OK and then Continue to produce the report.

### A Note About Input Files and Date Parameters

If you intend to use an input file with a date parameter for the Route Delivery List, you must follow a specific procedure when building the input file to prevent certain date-related validation issues.

#### To build an input file using a date parameter:

1. Select the Route Delivery List option from the menu.
2. Click Add and select the Product.
3. In the Report Date field, press Ctrl-P to display the input parameter dialog box.
4. Enter the Parameter Name (e.g., TODAY + 1) and click OK.<br>

   ![](https://1417315899-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1ToZXx8io0JJXNBRcPOt%2Fuploads%2FZbUHwu0yhoJbJl8Rqxw8%2FRoute%20Delivery%20List%20-%20Parameter%20Name.png?alt=media\&token=35515be1-efe2-43c9-9c01-49b5f0c7416b)
5. Back in the Report Date field, enter a date that is many years into the future (e.g., 01/01/2050).
6. Complete the rest of the fields on the window as appropriate and click OK.
7. Click Save, enter a name for the input file, and click OK. The input file is now saved and can be used the next time you run the Route Delivery List.
8. On the Route Delivery List Report window, click Cancel.

#### To use the input file:

1. Select the Route Delivery List option from the menu.
2. Click Find, enter the input file name, and click OK.

#### Example—Route Delivery List

![](https://1417315899-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1ToZXx8io0JJXNBRcPOt%2Fuploads%2F285A6YMNH9gXrPE7pgCr%2FExample%E2%80%94Route%20Delivery%20List.png?alt=media\&token=8030cb0f-d68b-499b-a627-7e879255334c)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.navigaglobal.com/circulation-user-manual/reporting/route-menu/route-delivery-list.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
