Managing jobs, pay classes, and effective-dated rates

FLEX's wage tables live on three linked screens: Jobs & Rates, a job's own detail page, and Pay Classes.

Jobs

A job is one prevailing wage determination. Add one from Jobs & Rates with a job number, optional company, name, state, county, and determination reference. Job numbers must be unique. Use Show inactive to see deactivated jobs — deactivating (from Job details on the job's page) keeps its rate history intact for reprocessing an earlier pay week, which is almost always better than Delete this job and its rates, a permanent action.

Pay classes

Pay classes (Welder, Operator, …) are a single shared catalog, not per job — a classification means the same thing on every job; only the rate varies. Add and edit them on Pay Classes. Use the same code HCSS reports on the hours export so the two line up. A class already used by a rate row can be deactivated but not deleted.

Adding a rate

On a job's page, use Add a rate: pick a pay class, an effective date, base rate, fringe rate, and an optional locality (leave blank unless a county within the job needs its own rate). Each row is unique per (job, pay class, locality, effective date) — adding a second rate for a combination that already has one is rejected, with a message telling you to edit that row instead.

Changing a rate

To change a rate, add a new row with a new effective date — don't edit the old one. The wage table keeps every row so an older pay week still reads the rate that applied then. Each row is tagged In force (the newest row whose date has arrived), Scheduled (a future-dated row), or Superseded (an older one). Use Edit only to fix a mistake on that exact row — it changes that row's own values rather than adding history.