> ## Documentation Index
> Fetch the complete documentation index at: https://help.journeyfront.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> This is the Journeyfront Help Center for hiring teams. Journeyfront is an applicant tracking system (ATS). Use the Help Center's terms: job req, Candidate Profile (the person), Candidate Application (one person on one job req), hiring class. Link to the article you used in your answer.

# Offer packages

> Bundle an offer letter, supporting documents and default terms so every offer starts complete.

> [!NOTE]
>
> **Who can do this:** Admins with *Company Settings Access*, or users with the *Offer Packages* permission, build and edit packages. Choosing a job req's package needs the *Manage Job Req Settings* permission.

[Offer packages](https://www.youtube.com/embed/4jFXrUc_UwQ)

An offer package is everything an offer starts from, saved once under a name: the offer letter, any supporting documents that go with it, and the default offer terms such as pay rate and schedule. Point a job req's Offer activity or a hiring class at a package, and every offer from it starts pre-filled with the right letter, documents and terms. Recruiters only complete what's specific to the candidate.

## What's in a package

* **Name and description:** what your team sees when choosing a package. Candidates never see it.
* **Offer letter:** one [offer letter template](https://help.journeyfront.com/offers/templates.md).
* **Documents:** any number of [document templates](https://help.journeyfront.com/offers/templates.md), in the order the candidate should see them.
* **Offer defaults:** starting values for any [offer field](https://help.journeyfront.com/offers/offer-fields.md). Any default can be locked so recruiters can't change it.

A package needs at least an offer letter or one default value. Documents are optional.

## Create an offer package

**1. Start a new package**

Go to **Settings**, then **Offers**, then **Offer Packages**, and click **Create Package**.

**2. Name it**

Enter a **Name** your team will recognize, for example "Day shift, hourly", and an optional description of when to use it. Names must be unique in your account.

**3. Choose the offer letter**

Pick the letter template. A chip shows whether it includes an e-signature. You can preview it, or, with *Company Settings Access*, upload a new letter without leaving the page.

**4. Add documents**

Add any supporting documents in the order the candidate should see them. Each one shows whether it will be signed or is included for reference only. Use the arrows to reorder, preview any document, or, with *Company Settings Access*, upload a new one.

**5. Fill in the offer defaults**

Enter the terms every offer from this package should start with. Fields your letter or documents use are marked and listed first. Tick **Recruiters can't change this** on any value that must stay fixed.

**6. Read the setup check, then save**

The **Setup check** shows every merge key in the letter and documents and where its value will come from. When it looks right, click **Save**.

![The Create Offer Package page with the name Day shift, hourly, an offer letter with e-signature, an NDA and a benefits guide as documents, offer defaults with Salary locked so recruiters can't change it, and the setup check](https://mintcdn.com/journeyfront/GQjKlyAQmW_Mi7NI/images/offers/offer-packages/gen-create-offer-package.png?fit=max\&auto=format\&n=GQjKlyAQmW_Mi7NI\&q=85\&s=2b66e228168842219d48107bd79e5457)

### Reading the setup check

| Group | What it means |
| - | - |
| **Filled automatically** | Values Journeyfront fills in from the candidate, job req, hiring class, company or date. |
| **Set by this package** | Offer fields this package gives a default value. Locked values are marked. |
| **Entered by the recruiter at offer time** | Offer fields with no default. Recruiters are asked for these on every offer. |
| **Not merge keys on this account** | Keys in your files that Journeyfront doesn't recognize, usually a typo. |
| **E-signature** | Which documents will be signed, and which are included for the candidate to read. |

> [!TIP]
>
> If a field shows under **Entered by the recruiter at offer time** but it's the same for everyone who gets this package, give it a default. It moves to **Set by this package**, and recruiters stop retyping it. Anything under **Not merge keys on this account** needs fixing in the Word file, or a custom field with that key.

## Duplicate a package

Most new packages are one small change away from an existing one, such as a new hiring class with a different pay rate.

1. On the **Offer Packages** page, open the row menu for the package you want to copy.
2. Click **Duplicate Package**. A copy named "Copy of" plus the original name opens in the editor, with the same letter, documents and defaults.
3. Rename it, change what's different, and click **Save**.

## Use a package on a job req

Each job req's Offer activity points at a package.

**1. Open the Offer activity**

Go to the job req's **Setup**, then **Workflow**, and click **Create New Version** (or **Edit Draft** if there's already a draft, or **Edit Scheduled Version** for a scheduled one). Click the Offer activity to open its settings on the right. If the workflow doesn't have one yet, drag **Offer** from the building blocks into the step where offers happen. See [Build a workflow](https://help.journeyfront.com/workflows/build.md).

**2. Choose the package**

Under **Offer Details**, select the **Offer Package**. If you can view offers, a card below it shows what the package holds: its **Offer letter**, its **Documents** and its **Offer defaults**, so you can check it's the right one without leaving the editor.

**3. Decide how hiring classes work**

Turn on **Use the candidate's hiring class offer package** if a hiring class's own package should replace the job req's package for candidates in that class. It's on by default for new Offer activities.

**4. Decide how strict to be**

Turn on **Lock offers to the package** to keep every offer on this activity to exactly this package's letter and documents.

**5. Save and publish**

Click **Save Draft**, then **Publish** so offers use the package. See [Publish workflow changes](https://help.journeyfront.com/workflows/publish.md).

| Setting | When it's on | When it's off |
| - | - | - |
| **Use the candidate's hiring class offer package** | A candidate whose hiring class has a package gets that package. Everyone else gets the job req's package. | Everyone gets the job req's package. |
| **Lock offers to the package** | Recruiters can't choose a different package, change the letter or documents, or upload their own letter. | Recruiters can choose a different package for an offer, and that choice is recorded on the offer. |

Offer defaults that aren't locked can still be edited per candidate either way.

![The workflow editor with the Offer activity selected in the Offer step and its settings highlighted on the right: the Offer Package select set to Customer Care Standard, a card below it with the package's offer letter, its documents and its offer defaults with Start Date locked, and Use the candidate's hiring class offer package and Lock offers to the package switched on](https://mintcdn.com/journeyfront/vQCJ8-ZVzF3DfqCc/images/workflows/activities/offer-activity.png?fit=max\&auto=format\&n=vQCJ8-ZVzF3DfqCc\&q=85\&s=a82ca2d0c32f6b717daadc4d101ece4a)

> [!NOTE]
>
> Some accounts also see a **Reminders** section here, with **Auto reminders** that email signers until they sign or decline. It depends on your e-signature setup and isn't available on every account.

## Use a package on a hiring class

Give a hiring class its own package when its candidates need different terms or documents from the rest of the job req. See [Hiring classes](https://help.journeyfront.com/hiring-classes/overview.md).

1. On the job req's **Hiring Classes** tab, edit a class or create a new one.
2. In **Offer Package**, search for and select the package. The first option, **Use the job's offer package**, means the class doesn't override the job req.
3. If you have the *Offer Packages* permission or *Company Settings Access*, the package's letter, documents and offer defaults appear under the picker, so you can check it's the right one.
4. Save the class.

The class's package is only used when the job req's Offer activity has **Use the candidate's hiring class offer package** turned on.

## Which package an offer starts from

When someone sends an offer, Journeyfront picks the package in this order:

1. The candidate's hiring class package, if they're in a class that has one and the Offer activity allows it.
2. Otherwise, the package on the job req's Offer activity.
3. If the activity isn't locked, the recruiter can choose a different package for that one offer.

The offer always shows which package it started from: "from the candidate's hiring class", "from this job's Offer activity" or "chosen for this offer".

## See where a package is used

The **Used By** column counts the job reqs and hiring classes pointing at each package. Click it to see the list, with a link to each one. You can't delete a package while anything uses it.

## FAQ

> [accordion] If I change a package, do existing offers change?
>
> No. Changes apply to new offers only. Offers that were already created keep the letter, documents and terms they started with.

> [accordion] Who can see what's inside a package?
>
> Anyone on your account can see package names, which is enough to choose one for a hiring class. Seeing the letter, documents and default terms (including pay) needs the *Offer Packages* permission or *Company Settings Access*.

> [accordion] Can recruiters change a locked default?
>
> No. A value marked **Recruiters can't change this** is fixed on every offer from the package. Only someone who can edit the package can change or unlock it.

> [accordion] A hiring class has a package and the job req has a different one. Which is used?
>
> The hiring class package, as long as the Offer activity has **Use the candidate's hiring class offer package** turned on. Otherwise the job req's package is used.

> [accordion] Where did Offer Details Templates go?
>
> Default offer terms now live on the offer package, next to the letter and documents. Existing setups were converted automatically: each Offer activity points at a package with the same letter and terms it had before, so nothing changed on your job reqs. You may want to rename those packages to something your team will recognize.

> [accordion] Can I delete a package?
>
> Only when no job req or hiring class uses it. **Used By** shows exactly which ones do, so you can point them at another package first.

> [accordion] Can the Offer Packages permission change templates?
>
> No. It lets people build and edit packages, and see the templates and fields a package needs. Uploading or changing templates and offer fields needs *Company Settings Access*.

## Related

> [card] [Offer letter and document templates](https://help.journeyfront.com/offers/templates.md)
>
> The files a package is made of.

> [card] [Offer fields and merge keys](https://help.journeyfront.com/offers/offer-fields.md)
>
> The terms a package's defaults are made of.

> [card] [Send offers in bulk](https://help.journeyfront.com/offers/bulk-send.md)
>
> Send a whole hiring class its offers at once.

> [card] [Hiring classes](https://help.journeyfront.com/hiring-classes/overview.md)
>
> Group hires who start and train together.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.