Troubleshoot common contract and jobsite data issues¶
As a Contract role user, I want to recognize the config/data-model patterns behind recurring "this looks broken" tickets in Contracts and Jobsite, so that I can tell a real defect apart from expected (if confusing) system behavior before escalating or re-entering data that was already correct.
Screens: Contracts (all tabs), Jobsite (all tabs)
This page is mostly fact, not procedure — these are the recurring mechanisms behind closed ClickUp cases in this module (18 Contract-group cases, 42 Jobsite-group cases), grouped by root cause rather than by individual ticket. The goal is to teach the underlying mechanism once per cluster, since that's what you'll actually need to reason through when a similar-looking but new issue shows up.
Things to watch out for¶
Static bar \"Multiple\" and two-job members break single-job assumptions everywhere
A worker with two concurrent open work records (e.g. a jobsite job plus a JobDesk record) breaks several single-job assumptions across the UI — the static bar now shows "Multiple" instead of one rate, and the Change History report shows current rate + effective date per work record instead of a single from/to delta (because two-job members have no single "from/to"). A known residual gap: terminations show on the member's own Change History tab but not on the Change History report. Any single-job assumption in PRIZM's UI is suspect when the member in question has two concurrent jobs. (IUOE-1785, IUOE-2483)
\"Previously Employed\" and Trade Code display both flow from the same contract/work-record linkage
If a trade code looks wrong (e.g. shows a member's earliest code instead of their current one) or a member who should be inactive-but-listed is missing from a jobsite roster, both symptoms trace back to the same mechanism: the work-record model and its linked contract govern trade-code selectability and the "Previously Employed" checkbox's display state together, not independently. The separate "all" filter checkbox on the Members tab reliably shows every member who ever worked a site regardless of this desync — use it as a practical workaround while confirming whether the underlying display bug has recurred. Also check the jobsite's Contract association directly: a Trade Code can be unavailable for a Job Referral Jobsite specifically because the linked Contract (not just the jobsite's own Trade Code list) governs which codes are selectable on a work record. (IUOE-2368, IUOE-1792, IUOE-1786)
\"Contacts aren't showing\" has two distinct root causes — don't assume either one by default
A stale-grid-refresh pattern (re-navigating away from and back to a tab fixes it) explains some "active contacts not showing by default" symptoms — distinct from the top-bar quick-switch stale-grid bug covered in Create and maintain a jobsite. Other "contacts/data grid is blank" symptoms instead trace to upstream data quality — historically, a non-numeric Employer "number" field (literal text like a company name instead of a number) caused blank data grids after adding a management company; Employer numbers are now autogenerated to prevent this. Before troubleshooting further, figure out which of the two you're looking at: try re-navigating first (cheap), then check the Employer's number field for anything non-numeric. (IUOE-2682, IUOE-1908)
Job Title on an Employer contact isn't used in invoice generation
Job Title was added to Employer contacts (it was already present on Jobsite/Management Co contacts) purely for data-preservation parity with legacy Union Solutions — it's confirmed not used in invoice generation. If an invoice recipient looks wrong, check Contact Type, not Job Title. (IUOE-2229)
Repeat-regression-prone jobsite reports are worth a specific release-to-release recheck
The Employer/Jobsite list report's column-header labeling has been fixed, regressed, and fixed again across consecutive releases (2.18 fix, 2.19 regression, 2.20 re-fix) — and a separate Jobsite Profile report fix (duplicated comments, mislabeled Active/Inactive header) had its own roster-grouping regression caught during retest. When retesting a "fixed" jobsite report, also check that the fix didn't silently regress an unrelated feature of the same report (grouping, headers) — this cluster shows it happening more than once. (IUOE-2043, IUOE-2508)
Very large legacy SALT jobsite numbers are a known historical artifact
Jobsite auto-numbering previously generated huge date-stamp-derived numbers inherited from legacy SALT sites. This was fixed by excluding those legacy records from the auto-number calculation going forward (rather than renumbering existing history) — if you see an oddly huge jobsite number on an older SALT-origin record, that's the known artifact, not a data error, and not a pattern to replicate manually on a new jobsite. (IUOE-2219)
Override-popup SUBMIT can discard the override you just entered
On the dues/wage rate override popup (reached from a member's work record), clicking SUBMIT has been observed to actually discard the override and revert the work record, while Cancel updates the static bar/change history but doesn't display the new rate until the record is reopened. This is a real, confusing trap for anyone doing rate overrides — if an override "didn't stick," check which button was actually clicked before assuming a data bug. (IUOE-2163)
The single most training-relevant fact in this module: dues/wage rate comes from change history, not a dedicated field
Dues Assessment and related reporting reads a member's dues/wage rate from work-record change history, not a separate assessment-history store. A rate correction made on the Contract or Jobsite Rates tab doesn't retroactively fix a member whose own change-history data is stale or wrong at the source — that's a different, per-member correction. This mental-model gap sits behind more than one closed ticket in this module, including members assessed an incorrect minimum rate because of stale legacy change-history data. (IUOE-2131)
Rates tab questions (jobsite-level) don't have a confirmed-resolution writeup yet
Jobsite Rates tab requests — inline editability after adding a rate, adding a Dues rate column, Start Date sort not working in the grid — are all still Phase 1 stubs with no confirmed resolution detail preserved. If a Rates-tab question comes up that isn't covered by Maintain contract rates and dates or Create and maintain a jobsite, flag it for follow-up rather than assuming it's already resolved.
Related: Create a new contract, Maintain contract rates and dates, Create and maintain a jobsite.