Edit Job Code Mappings

---

At a glance

Editing a Job Code mapping changes which payroll and labor category a position's hours flow into from this point forward. Changes are forward-only: hours already worked under the old mapping stay attributed to the old Job Code in historical reports, so plan the change carefully around payroll boundaries.

Before you start

1. You need a role with permission to manage Job Code mappings. Check your customization rubric, or ask whoever configures roles at your store. [VERIFY: exact permission label, likely Manage Job Codes or Manage Positions.]
2. Confirm the new Job Code is already available in OneClick. For stores that use HotSchedules, the code must exist in HotSchedules and must have synced; for stores that do not use HotSchedules, the code must be defined in the OneClick Job Codes setup area. See Understand Job Codes for the source-of-truth model.
3. Consider the timing. Changes are forward-only; hours worked before the save stay under the old Job Code. If your payroll cutoff is tomorrow and you change a mapping today, today's hours go to the new code and yesterday's go to the old. Plan the change at a clean boundary when possible (start of week, start of pay period).
4. If multiple positions need the same update, plan to make them in a single session so the reporting boundary is consistent across positions.
5. Estimated time: under two minutes per position.

Steps

Path A: Change a position's Job Code

Use this path when a position's Job Code should be different from what it currently is, but a Job Code is still needed.

1. [VERIFY: navigation path to the position list or Job Code assignment surface.] Open the position you want to re-map.
2. Open the Job Code assignment control. [VERIFY: whether this is a three-dot menu, an inline edit pencil, a dropdown on the row, or a dedicated edit screen.]
3. Select the new Job Code from the available list. If your store uses HotSchedules and the code is not in the list, confirm the code exists in HotSchedules and has synced (see the gotcha on sync lag below).
4. Save the change. [VERIFY: whether save is explicit (Save button) or implicit (closing the control persists).]
5. Verify. The position should display the new Job Code in the position list. Going forward, hours worked in this position roll up to the new Job Code in labor reports.

Path B: Remove a Job Code mapping

Use this path only when a position should no longer have any Job Code attribution. This is rare and usually implies the position itself should be deactivated rather than left active without a Job Code.

1. Open the position as in Path A.
2. Open the Job Code assignment control.
3. Clear the Job Code selection. [VERIFY: whether an explicit Clear or None option exists, or whether the control requires you to delete the current selection another way.]
4. Save.
5. Be aware of the consequence: a position without a Job Code will produce unmapped hours in labor reports. If the position is active and scheduled, those hours will appear as an unmapped anomaly in reporting until either a new Job Code is assigned or the position is deactivated. Plan the next step accordingly.

Path C: Correct historical attribution after a mapping change

Changes are forward-only by design. Once a mapping has been changed, hours already worked under the old mapping stay under the old Job Code in historical reports. If you discover that a position was mapped to the wrong Job Code for a period that has already been paid out or reported on, OneClick cannot self-serve correct the history.

1. Change the mapping going forward using Path A.
2. Gather the context for the historical period: which position, which Job Code was wrong, what Job Code should have been there, and the affected date range.
3. Submit a support ticket. Historical correction is a manual operation that support performs once the forward mapping is clean.
4. Include the same evidence in the ticket that you would need for a payroll adjustment: team member names, shift dates, hours, and the affected labor report. Support uses this to issue the correction.

Video

Video coming soon.

Common gotchas

I changed the Job Code and the labor report for last week still shows the old one.

Working as designed. Job Code mappings apply going forward from the moment of the change. The labor report for last week reflects what the mapping was last week. If you need the historical report corrected, go through Path C above.

The new Job Code I need is not in the list.

Path-dependent. If your store uses HotSchedules, the code either has not been created in HotSchedules yet, or has been created but the sync has not run. Confirm the code exists in HotSchedules first; if it does, wait for the next sync. [VERIFY: typical sync cadence and whether a manual sync trigger exists.] If your store does not use HotSchedules, open the OneClick Job Codes setup area and create the code there before returning to the mapping edit.

I want to change a Job Code for one shift only, not for the position permanently.

Not supported through the mapping. The Job Code is a property of the position; changing it affects all future hours in that position. If a team member needs hours attributed to a different Job Code for a specific shift, the correct lever is to schedule them into a different position for that shift, one that already carries the target Job Code. See Understand Job Codes for why Job Codes follow the position, not the person.

I want to change a Job Code for just one team member in a position.

Not supported. Per-team-member Job Code overrides do not exist. Hours in a position are attributed to the position's Job Code, the same for every team member. If a specific team member should have different attribution, they need to be scheduled into a different position.

The position shows two Job Codes in reporting.

A position carries one Job Code. If two appear, you are probably looking at a report that spans a mapping change: some hours under the previous Job Code, some under the new one. Confirm the date range and look for a mapping change in that window. If the position list itself appears to show two Job Codes for one position, submit a support ticket with a screenshot.

I changed a mapping on one store. The same position at another store in my organization still has the old Job Code.

Job Code mappings are per store. In a multi-store organization, each store has its own position list and its own mappings. If you want consistent mappings across stores, apply the change at each store individually. If your stores' positions were set up from a shared template, the template is a one-time copy, not a live link; changes do not propagate automatically.

Two leaders edited the same position at the same time and one of the Job Codes reverted.

Last writer wins on position edits. If two leaders are making changes to the same position in close succession, coordinate before saving, or have a single person own the change set. The Layout Editor has the same behavior; concurrent editing is not safe in either surface.

I need to change dozens of mappings at once.

There is no bulk-edit surface today. Edit each position individually. For multi-store organizations applying the same change everywhere, the fastest option is to document the target mapping in your customization rubric and walk through positions store by store. If the volume is high, contact support; they can sometimes apply configuration changes in bulk on the operator's behalf.

A position shows no Job Code after I tried to edit.

The save may not have taken, or the new Job Code may have been cleared without a replacement. Open the position and re-assign a Job Code. An unmapped position produces unmapped hours in reporting; fix it before the next shift runs.

Related articles

1. Assign a Job Code to a Position (How-To Guides) for first-time mapping.
2. Understand Job Codes (Reference) for the source-of-truth model and the position-carries-the-Job-Code principle.
3. Add a Position (How-To Guides) for creating a new position that will need a Job Code.
4. Understand Your Customization Rubric (Reference) for tracking which roles can edit mappings.
5. Request a Permission Change (How-To Guides) if the Manage Job Codes permission is missing.
6. Understand Permission Levels (Reference) for the role-to-permission model.

Still stuck

If a mapping change does not save, the correct Job Code is not available in the list even after confirming it exists upstream, or labor reports show unexpected behavior after a change, submit a support ticket and include:

1. Your store number.
2. Whether your store uses HotSchedules.
3. The position name and its current Job Code.
4. The intended Job Code.
5. A screenshot of the assignment screen before and after the attempted save.
6. If the issue is a reporting mismatch, the date range and the affected team members.

Support typically responds within one business day.

---

Pre-publish checklist

29 65eea752-f5cd-4eaf-83a2-eaa070ae6d43 complete Seven sections filled.

30 fd9b1aa5-6dc6-44b2-84fa-b9327450bcb4 complete Multi-path How-To (change, remove, historical correction).

31 407bdec6-d0b4-4f73-8383-53a1ad147d8a complete Forward-only attribution behavior surfaced at the top of At a glance and in multiple gotchas.

32 d1609948-4c3f-43b4-a404-3a5d4d839966 complete HotSchedules-vs-OneClick-native path coverage inherited from Understand Job Codes.

33 12a4fb9b-74aa-4005-949b-2fbe591f04c4 complete No em dashes.

34 f52ebfd5-a202-433e-9e2f-b2a4926139a8 complete No hedge words.

35 ef43d65c-a53e-427a-b6b2-fb5fe9dcb1ef complete Permission-based role references.

36 6b138644-021f-4b3f-86ce-58f61bc665c9 complete Voice: leader, not operator.

37 81cfe523-fdb8-463a-8747-f41735416574 complete No real identifying data.

38 d6230f50-b568-4cc8-a572-b29d95036c1d complete Concurrent-editing gotcha.

39 37a6c61f-6802-4fa3-bf83-7fdd7594981e complete Per-store scope call-out for multi-store organizations.

40 142a4e00-a322-40df-8c75-92d85047940a complete At a glance trimmed to 2 sentences (Turn 60).

41 1cbbbdc8-8bfa-40f7-acdd-78e756f26d2c incomplete UI verified against Production (VERIFY blocks in Steps).

42 8c92ddff-944e-46f3-9008-b96625519e55 incomplete Screenshots at decision points (position list with Job Code column; assignment control; save confirmation; labor report showing pre-change and post-change attribution).

43 8d86b104-4a2c-42e4-833a-52517c5bc8d4 incomplete Reviewed by Jared and Kevin.

Why this article exists

Surfaced by the Wave 1 cross-link map Pass 3 Batch 3 audit (Turn 45, Flag 42). Both Assign a Job Code to a Position and Understand Job Codes reference "Edit Job Code Mappings" as a placeholder, indicating that the distinction between first-time assignment and subsequent editing is meaningful enough that leaders look for separate guidance. Job Codes are a recurring support ticket source for three reasons, and this article tries to deflect all three: the mapping-is-forward-only surprise in labor reports, the HotSchedules sync path that sometimes makes a needed Job Code unavailable, and the per-store scope that surprises multi-store operators who expect a change to propagate. Approved for drafting via the Flag 42 Placeholder Decision Memo (pageId 397344811), Turn 48, as priority 2 in the drafting queue.

Source

Derived from Understand Job Codes v2 (394526728) for the conceptual spine (HotSchedules-sourced vs OneClick-native, position-carries-the-Job-Code, forward-only attribution) and Assign a Job Code to a Position v2 (394887188) for the in-product workflow mechanics. No new VERIFY blocks relative to the two source articles; UI specifics for the edit control remain to be verified against Production, consistent with open VERIFY blocks on Assign a Job Code to a Position.