At the header level, Special Jobs can only be linked to one Client and one Location at a time. This architecture ensures that every one-off intervention is correctly contextualized within your operational hierarchy.


However, you can manage an improvement task across multiple physical areas by using a broader Parent Location combined with Infraspeak's Ad-hoc Task List, or by creating separate jobs if the locations belong to completely different facilities.




TABLE OF CONTENTS


1. Understanding the Header-Level Rule


Infraspeak requires every Special Job to be mandatorily associated with one Client and one Location at the header level.


This strict relationship protects your operational data. It guarantees that cost metrics, technician assignments, SLA timelines, and asset histories are cleanly tracked without cross-contaminating unrelated facilities.



2. Workarounds


2.1 Scenario A: Working Within the Same Building


If you are carrying out an improvement task (e.g., installing new emergency signage) across multiple physical areas inside the same general facility, you do not need to create separate jobs. Instead, utilize the Ad-hoc Task List:


  1. Step 1 - Select a Parent Location: When creating the Special Job, choose a higher-level "Location" at the header (such as the general Building or Facility) that encompasses all the smaller areas.

  2. Step 2 - Detail Specific Areas in the Ad-hoc Task List: Unlike standard planned maintenance, Special Jobs let you build a custom, one-off checklist on the fly. Create individual task lines specifying the exact spot and task (e.g., "Install signage in Staircase A", "Install signage in Staircase B"), defining exact quantities for each.


2.2 Scenario B: Working Across Completely Different Buildings/Clients


If the physical locations belong to entirely different buildings, clients, or properties, the parent location workaround will not work. To ensure work orders generate, route, and report accurately, you must construct a unique job for each primary site:

  1. Step 1 - Create the Baseline: Set up the first job, fully detailing the scope, tasks, and required checklists for the first building.

  2. Step 2 - Duplicate for Other Locations: Replicate or copy the job, changing only the Client/Location header field for each subsequent property (e.g., Job 1 for Building Alpha, Job 2 for Building Beta).


Note: Utilize Templates - Draft a master template for recurring improvements so that creating copies across your buildings takes only a few clicks.