> For the complete documentation index, see [llms.txt](https://docs.paragontruss.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paragontruss.com/markup/before-you-start/create-a-practice-job.md).

# Create a Practice Job

A practice job gives you a safe place to set up templates and rehearse sealing without impacting a real customer job. You use it in [Create and Set Up Sealing Templates](https://docs.paragontruss.com/markup/how-to-guides/create-and-set-up-sealing-templates).

Before you begin, zip one portrait PDF and one landscape PDF together, and register a seal for at least one state. See [Register Seals and Signatures](https://docs.paragontruss.com/markup/before-you-start/register-seals-and-signatures).

## Create the job in Paragon Review

### Step 1 - Click `Create Job`

Sign in to [review.paragontruss.com](https://review.paragontruss.com/) first. The job panel opens above the jobs grid.

### Step 2 - Click `Choose a .zip file` and choose your .zip of test PDFs

When Paragon Review has read the files, the `File Manager` opens.

### Step 3 - Click `Move All`

`Move All` is the double arrow between the columns. Plain PDFs land in `Miscellaneous Files`, which Markup doesn't show; this moves them all to `Other PDFs to Seal`.

{% hint style="info" %}
Note

Files that share the same base name, such as `JOB_00421.pdf`, `JOB_00421.tre`, and `JOB_00421.ans`, are treated as one linked component and go to `Components to Seal` on their own. Linked components behave differently in Markup than a plain PDF. For a practice job, a .zip of PDFs is all you need.
{% endhint %}

### Step 4 - Click `Confirm`

### Step 5 - Enter a name, such as `Markup Practice` in `Name`

### Step 6 - Choose a region you have a registered seal for, such as `Maryland` for `Select Region(s)`

You need a registered seal for the job's region to seal it.

### Step 7 - Choose a job type, such as `Seal` for `Select Job Type`

### Step 8 - Choose who to share the job with, such as `Do not share` for `Share With`

`Do not share` keeps the practice job in your organization.

### Step 9 - Click `Create Job`

Fill in any other required fields first. If one is empty, such as `Design Program` or `Plate Manufacturer`, it's outlined in red and the job isn't created. Fill it in and click `Create Job` again. For every field, see [Create a Job](https://docs.paragontruss.com/review/how-to-guides/create-a-job) in the Paragon Review docs.

## Open the job in Markup

### Step 1 - Click the job's name in the grid

### Step 2 - Click `Open Job`

Markup opens in a new tab with the job's PDFs loaded. If Paragon Review is still preparing the files, a message says "Preprocessing is not yet complete." Try again in a minute.

### Step 3 - Click `Available Templates`

`Annotation Tools` is found in the left sidebar, and opens the template list on the right. A new organization has only the original, default system templates, marked "(System)", such as the cover page and back page, and no sealing templates yet. You add those next.

## Optional: test the full request workflow

To see how real jobs arrive, send yourself a seal request from Paragon Design: create a shared set of trusses and request seals for one of your registered regions. See [Share Trusses and Request Seals or Repairs](https://docs.paragontruss.com/design/how-to/general/share-trusses-and-request-seals-or-repairs). Then refresh Review and open the new job.

## Next step

[Create and Set Up Sealing Templates](https://docs.paragontruss.com/markup/how-to-guides/create-and-set-up-sealing-templates)


---

# 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://docs.paragontruss.com/markup/before-you-start/create-a-practice-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.
