> ## 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 fields and merge keys

> Define the terms every offer captures, and use merge keys to put any value into your offer letters and documents.

> [!NOTE]
>
> **Who can do this:** Admins with *Company Settings Access*.

**Offer fields** are the terms of an offer: salary, start date, employment type, pay frequency, bonus, hiring manager and anything else your offers need. **Merge keys** are the keys, like `{{SALARY}}` or `{{CANDIDATE_NAME}}`, that place values into your offer letters and documents. Every offer field has a merge key, and so do the candidate, job req, hiring class and company details Journeyfront already knows, so your documents fill themselves in.

## Offer fields

Offer fields appear on the offer form your team completes when sending an offer, and they're what an [offer package](https://help.journeyfront.com/offers/offer-packages.md) can pre-fill and lock. They apply to every job req in your account.

Go to **Settings**, then **Offers**, then **Offer Fields**.

![The Offer Fields page in Settings, listing the default offer fields and a custom Sign-On Bonus field with their types, merge keys and required status, with the + Field button highlighted](https://mintcdn.com/journeyfront/GQjKlyAQmW_Mi7NI/images/offers/offer-fields/gen-offer-fields-page.png?fit=max\&auto=format\&n=GQjKlyAQmW_Mi7NI\&q=85\&s=f173e895258121b40b657386974e391c)

### Default fields

Every account starts with these offer fields:

| Field | Type | Merge key | Required by default |
| - | - | - | - |
| Job Title | Short Text | `{{JOB_TITLE}}` | Yes |
| Start Date | Date | `{{START_DATE}}` | Yes |
| Today's Date | Date | `{{TODAYS_DATE}}` | No |
| Offer Expiration Date | Date | `{{OFFER_EXPIRATION_DATE}}` | No |
| Employment type | Multiple Choice | `{{EMPLOYMENT_TYPE}}` | No |
| Salary | Currency | `{{SALARY}}` | No |
| Pay Frequency | Multiple Choice | `{{PAY_FREQUENCY}}` | No |
| Bonus | Currency | `{{BONUS}}` | No |
| Options | Number | `{{OPTIONS}}` | No |
| Hiring Manager | User | `{{HIRING_MANAGER}}` | No |
| Notes | Long Text | `{{NOTES}}` | No |

Job Title fills in from the job req (its external job title, if it has one) and Today's Date from the day the offer is created, unless a package or recruiter sets them. In **Send Offer**, the Offer Expiration Date also becomes the default expiry for the [e-signature request](https://help.journeyfront.com/offers/e-signatures.md).

On a default field you can change the description and whether it's required. Its label, type and options are fixed, and it can't be deleted.

### Add an offer field

**1. Click + Field**

It's at the top right of the **Offer Fields** page.

**2. Describe the field**

Enter the **Label** your team sees (for example "Sign-On Bonus"), an optional **Description**, and the **Field Type**. For Multiple Choice, add the options.

**3. Set the merge key**

In **Merge Key**, type the key that goes between the braces, for example `SIGN_ON_BONUS`. In your templates it becomes `{{SIGN_ON_BONUS}}`.

**4. Choose whether it's required**

Turn on **Required** if recruiters must enter it on every offer, then click **Save**.

### Field types

| Type | What it holds | Good for |
| - | - | - |
| Short Text | Single-line text | Department, shift name |
| Long Text | Multi-line text | Notes, special conditions |
| Number | A whole number | PTO days, stock options |
| Date | A date picker | Start date, expiration date |
| Currency | An amount with a currency | Salary, bonus |
| Multiple Choice | A dropdown of your options | Employment type, pay frequency |
| User | A user on your account | Hiring manager, recruiter |
| Yes/No | A yes or no answer | Relocation offered, equipment provided |
| HRIS Object | A value from a list in your HRIS | Department, location or cost center |

### Edit, reorder or delete a field

* Click the **edit** icon on a row to change the label, description, required setting or options. The merge key can't be changed once saved, because your templates may already use it.
* Drag the **grip handle** on the left of a row to reorder fields. Recruiters see fields in this order when they send an offer.
* Click the **delete** icon to remove a field you added. Default fields can't be deleted.

> [!TIP]
>
> If a value is the same for everyone in a hiring class, such as the pay rate or schedule, don't make recruiters type it on every offer. Set it as a default on the class's [offer package](https://help.journeyfront.com/offers/offer-packages.md) instead.

## Merge keys

A merge key is a key in double curly braces that you type into a Word template, like `{{CANDIDATE_FIRST_NAME}}`. When Journeyfront generates the document for a candidate, it replaces each key with the real value from that Candidate Application. The values that went into each document are saved with it, so you always have a record of exactly what the candidate received.

### Built-in keys

These work in any template with no setup:

| Group | Examples | Filled from |
| - | - | - |
| Candidate | `{{CANDIDATE_NAME}}`, `{{CANDIDATE_FIRST_NAME}}`, `{{CANDIDATE_LAST_NAME}}`, `{{CANDIDATE_EMAIL}}`, `{{CANDIDATE_PHONE}}`, `{{CANDIDATE_ADDRESS_LINE_1}}`, `{{CANDIDATE_CITY}}`, `{{CANDIDATE_STATE}}`, `{{CANDIDATE_ZIP}}` | The Candidate Profile and the candidate's primary address |
| Job | `{{JOB_REQ_NAME}}`, `{{EXTERNAL_JOB_TITLE}}`, `{{JOB_CITY}}`, `{{JOB_STATE}}` | The job req |
| Company | `{{COMPANY_NAME}}` | Your account |
| Hiring Class | `{{HIRING_CLASS_NAME}}`, `{{HIRING_CLASS_START_DATE}}`, `{{HIRING_CLASS_LOCATION}}` | The candidate's hiring class, when they're in one |
| Date | `{{CURRENT_DATE}}` | The day the document is generated |
| E-Signature | `{{CANDIDATE_E_SIGNATURE}}`, `{{COMPANY_E_SIGNATURE}}` and their date and initials versions | Where people sign. See [signature fields](https://help.journeyfront.com/offers/templates.md#signature-fields). |

Your offer fields, and any personal or application fields you've given a key, use the key you chose.

### Give a personal or application field a merge key

Personal and application fields only need a key if you want them in a document. For example, you can put the candidate's preferred shift or their answer to a consent question straight into the offer letter.

**1. Open the field**

Go to **Settings**, then **Custom Fields**, then **Personal Fields** or **Application Fields**. Add a field with **+ Field**, or edit one that doesn't have a key yet.

**2. Enter the merge key**

In **Merge Key**, type the key between the braces. When you add a field, Journeyfront suggests one from the label, so "Preferred shift" becomes `PREFERRED_SHIFT`.

**3. Save**

The key now appears in the merge key reference and works in any template.

Merge keys follow the same rules everywhere:

* Upper-case letters, numbers and single underscores only.
* Unique across your account.
* Fixed once saved. You can change the field's label any time.

![The Add Personal Fields window with the Label Preferred shift and the Merge Key input highlighted, showing PREFERRED\_SHIFT between double curly braces with the format hint underneath](https://mintcdn.com/journeyfront/GQjKlyAQmW_Mi7NI/images/offers/offer-fields/gen-personal-field-merge-key.png?fit=max\&auto=format\&n=GQjKlyAQmW_Mi7NI\&q=85\&s=e7e2fa74bb940e01da566eafe1caac2e)

### Find the right key

Go to **Settings**, then **Offers**, then **Offer Letter Templates**, and open the **Merge Fields** reference. Keys are grouped by where their value comes from: Candidate, Job, Company, Hiring Class, Date, E-Signature, Offer Fields, and any custom fields you've given a key, such as Personal Fields and Application Fields. Search for a field and click its key to copy it, then paste it into your Word document.

![The Offer Letter Templates page in Settings with the Merge Fields reference, its search box and merge keys grouped by Candidate, Job, Company, Hiring Class, Date, E-Signature, Offer Fields and Personal Fields, with HIRING\_CLASS\_START\_DATE just copied to the clipboard](https://mintcdn.com/journeyfront/GQjKlyAQmW_Mi7NI/images/offers/offer-fields/gen-merge-fields-reference.png?fit=max\&auto=format\&n=GQjKlyAQmW_Mi7NI\&q=85\&s=910ffbc64baecf6a956a7e1d79a77325)

### How values appear in documents

| Field type | What's merged |
| - | - |
| Date | The date written out, for example "October 21, 2026" |
| Currency | The amount formatted with its currency symbol, for example "\$40,000.00" |
| Multiple Choice | The option's label |
| User | The person's full name |
| File upload | The file name |
| Address | The candidate's primary address, or their most recently updated address if none is marked primary |

### When a value is missing

Before any document is generated, Journeyfront shows every key the documents use and the value each candidate will get. Missing values are flagged. In **Send Offer**, candidate details such as phone, address and custom fields can be fixed right there and are saved to the Candidate Profile. Anything still missing has to be filled in, or you choose to leave it blank in the documents. Nothing is generated with a gap you didn't see. See [Send an offer](https://help.journeyfront.com/offers/send-offers.md).

## FAQ

> [accordion] What's the difference between a field's label and its merge key?
>
> The label is what your team sees on forms, for example "Sign-On Bonus". The merge key is the token you type into documents, for example `{{SIGN_ON_BONUS}}`. You can change a label any time; a key is fixed once saved. Personal and application fields also have an internal name, which is a free-text identifier and doesn't need to follow the key format.

> [accordion] Can I change a merge key after saving it?
>
> No. Your templates may already use it, and changing it would break them. If you need a different key, create a new field.

> [accordion] Where did the candidate name and address offer fields go?
>
> Candidate name, phone and address are built-in merge keys now, filled from the Candidate Profile. Recruiters don't type them on the offer form anymore. Use keys like `{{CANDIDATE_NAME}}` and `{{CANDIDATE_ADDRESS_LINE_1}}` in your templates.

> [accordion] Can I put a candidate's application answers in the offer letter?
>
> Yes. Give the application field a merge key, then add `{{YOUR_KEY}}` to the template. The candidate's answer for that Candidate Application is merged in.

> [accordion] I added a new offer field. Why isn't it in my letter?
>
> Existing templates only use the keys typed into them. Add the new key to your Word file and re-upload it. The template's **Used By** column shows which offer packages to check afterward.

> [accordion] Where do I set default values for offer fields?
>
> On an [offer package](https://help.journeyfront.com/offers/offer-packages.md). A package can pre-fill any offer field and lock it so recruiters can't change it.

> [accordion] Is there a limit on how many offer fields I can add?
>
> No. Add as many as your offers need, and keep the required ones to what recruiters really have to enter.

## Related

> [card] [Offer letter and document templates](https://help.journeyfront.com/offers/templates.md)
>
> Put merge keys and signature fields into your Word files.

> [card] [Offer packages](https://help.journeyfront.com/offers/offer-packages.md)
>
> Set default values and lock them.

> [card] [Custom fields](https://help.journeyfront.com/account-setup/custom-fields.md)
>
> Personal and application fields, and where they appear.

> [card] [Offers overview](https://help.journeyfront.com/offers/overview.md)
>
> How all the offer pieces fit together.


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