Why Is My Corrective Task Missing a Location? (How the Submission Location Step Works)

The Problem This Solves

When a corrective task is created from a checklist, it may appear with no location attached — meaning only admins and store managers can see it, and when a role is assigned, the task goes to that role at all locations instead of just the store where the checklist was submitted.

The fix is simple: Add the Select Location step to your template and enable the Submission Location toggle. Once you do, Xenia automatically carries the submitting store's location into every corrective task created from that template — no manual selection required.

How It Works

Part 1 — The Submission Location Toggle in the Template Builder

When you add a Location step type to your template, you'll see a toggle labeled Submission Location inside that step.

What this toggle does: It tells Xenia — "use this step's value as the official submission location for this form." Once enabled, whenever a corrective task is auto-created from this template (via conditional logic or a workflow), Xenia reads the location from this step and automatically pre-fills it into the corrective task.

The result: the corrective task is tagged to the correct store, the right role member at that store receives it, and only the people with access to that location can see it.

How to enable it:

1. Open your template → Edit → Builder tab
2. Add a step → select step type Location
3. Name it "Select Location" or similar
4. Look for the Submission Location toggle inside the step — toggle it ON (it turns purple)
5. Mark the step as Required
6. Save

Part 2 — Pre-fill from a Project (No Manual Selection Needed)

If the template is deployed via a Project, the location step pre-fills automatically — the employee completing the checklist doesn't have to select their store at all.

When a task is generated by a project, Xenia knows which location the task belongs to and pre-populates the Select Location step before the employee even opens the form. They see their store already filled in and simply move on to the rest of the checklist.

Any corrective task created from this submission automatically inherits that location — no coordinator needs to manually enter it, and no task goes to the wrong store.

Part 3 — What the Corrective Task Looks Like with Location Pre-Filled

When a corrective task is created from the submission, the location from the Select Location step is carried through automatically.

The purple banner at the top of the corrective task creation screen confirms exactly which location the task is being created for — "Creating Corrective Task for 064-Chicago - River North." The location is already locked in before the employee fills in any other field.

Summary — Three Scenarios

The rule: As long as the Select Location step is in the template with the Submission Location toggle ON, the corrective task always gets the correct location — regardless of whether the submission was from a project or submitted ad hoc.

Step-by-Step: Adding the Location Step to an Existing Template

1. Go to Operations → Templates → [Your Template] → Edit
2. In the Builder tab, click + Add Step near the top of the form
3. Select step type: Location
4. Name it: "Select Location"
5. Enable the Submission Location toggle — it turns purple when on
6. Check the Required checkbox
7. Move the step to the top of the form (drag it above all other steps)
8. Save and republish the template

Frequently Asked Questions

Can the location step be hidden so employees don't have to see it? If the checklist is assigned as a Project, the location pre-fills automatically and employees don't interact with it — it's effectively invisible to them. For ad hoc submissions (no project), the employee must select their location manually, as that selection is what provides the location data to the corrective task.

If I assign the task to a role, will it only go to that role at the submitting store? Yes — once the corrective task has a location, Xenia uses role × location membership to route to the correct person. Only the role member at the submitting store receives the task. Without a location on the task, the role assignment goes to every member of that role across all your locations.

Does this work for both auto-created tasks (workflows) and manually created tasks (from the step)? Yes. Both the Auto-Create Task from Template workflow action and the Require Corrective Task manual prompt respect the Submission Location step. As long as the step is in the template with the toggle enabled, both paths inherit the location correctly.

What if I already have corrective tasks going to the wrong locations? Add the Select Location step to the template now. Future submissions will create correctly-located corrective tasks. Past tasks that were already created will not be retroactively updated.


Need Help?
Reach out to our Support Team at Support@xenia.team