> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/card-layouts-designing-printing-encoding/batch-printing-and-or-encoding/performing-a-bureau-batch-job.md).

# Performing a Bureau Batch Job

**Note:** Personal Data Fields (PDFs), First Names and Last Names should not be put on card layouts that will be used for bureau printing/encoding. The following items can be included:

* Text or barcode fields linked to a card number
* Issue level and expiry date
* Manually entered information on the card layout.

There are some exclusions however, as listed below:

* A Text Object or Barcode Object that contains First Name, Last Name or PDF link fields (Note that Card Number is allowed)
* Image Object field linked to a PDF
* Morpho object whose properties say "Card Number + Biometrics" or "Card Number + Finger Vein"

1. Click **Configure** from the menu bar, then **Card Types**.

   The **Card Type** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. **Right click** on the required Card Type.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-7ee1d4fcb83ea500184e9ee19f70287651bbc80f%2Fbureau_encodingmenu.png?alt=media)
3. Select the appropriate option from the context menu:

   * **Batch Print Cards**
   * **Batch Encode Cards**
   * **Batch Print and Encode Cards**

   **Note:**

   These options are only enabled when **one** Card Type is selected, and only appear in the context menu when Facility Codes represented by the selected Card Type are licensed for Bureau Batch printing/ encoding.

   A Batch Job window displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-cdd7de3a21803c6df22c3990b73433ac5dec515c%2Fbureauprintcards.png?alt=media)

   **Note:**

   The title of this window will accurately reflect the option you selected, (i.e. ‘Batch Print Cards’, ‘Batch Encode Cards’ or ‘Batch Print and Encode Cards’).
4. Click the **Setup Printer…** button to alter the printer settings if necessary.

   **Note:**

   If you are encoding a MIFARE card with a printer connected via a serial port, you need to identify the port that the encoder is connected to. To do this:

   1. Click the **Setup Printer…** button to display the Printer properties.
   2. Click the **Encoding** tab.
   3. Select the port the encoder is connected to from the drop-down list.
5. Enter the **First Card Number** and **Last Card Number** of the cards to be printed/encoded.

   **Note:** You cannot print more cards than has already been set on the **Card Defaults** tab of the Card Type properties.
6. The **First Card Number** defaults to either:

   * what has been configured on the **Card Defaults** tab of the Card Type properties, or
   * if a Bureau Batch Job has already been performed previously for this Card Type, the last number used is remembered and it will be the next number.

   If required, change the card number to start at in the **First Card Number** field.
7. Select the appropriate **Reason for printing/encoding** from the drop-down list, or type your own reason into the text field. The reason selected will be logged in the event details.

   **Notes:**

   * The **Start** button will be disabled until a reason is entered if the **Operator must provide a reason for printing or encoding a card** checkbox was checked on the Photo ID Configuration window when “Reasons for Printing” were configured.
   * The **Read Card** button allows you to read a newly encoded card to verify the contents of this encoding. When clicked, the **Read MIFARE Card** dialog appears which uses the custom keys used to encode the cards when attempting to re-read the data on the card.
8. Click the **Start** button.

   The Status bar indicates the progress of the batch job, identifying the completed card count and the total card count, along with the card number of the card currently being printed.

   **Note:**

   While a batch job is in progress the **Start** button is replaced by **Pause** and the **Close** button is replaced by **Cancel**. If a problem is encountered with a particular card(s), an error message displays and an additional **Skip Card** button appears, allowing you to ignore any card that causes the Batch Job to fail.

   The **Cancel** button allows the Batch Job to be stopped and the Batch Job window returns to its original state. The **Continue** button allows you to restart a paused Batch Job, (e.g. a Batch Job could pause due to the card hopper being empty).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/card-layouts-designing-printing-encoding/batch-printing-and-or-encoding/performing-a-bureau-batch-job.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
