Skip to content

Maintain contract rates and dates

As a Contract role user, I want to keep a contract's wage rate schedule and key milestone dates current over the contract's life, so that members assigned to its jobsites get the right trade-code wage and the right benefit obligation dates keep triggering invoices on time.

Screen: Contracts > (a specific contract) > Rates tab, Dates tab

Rates: what's on the tab

The Rates tab is a trade-code hourly wage schedule for the contract — Trade Code, Trade Code Description, Hourly Wage, Dues Rate, Start Date, End Date, Static Rate — with filter checkboxes for "Show Only Active Records," "Rates From This Contract," and "Rates From Master Contract." Add Rate adds a new trade-code row; editing an existing row's Hourly Wage is how a wage change gets entered (Edit Wage).

This is a genuinely separate store from Contract Terms

Rates is trade-code-level hourly wage data; Contract Terms (Details tab) is whole-contract dollar-per-period benefit data. A contract can have real Contract Terms and still show 0 rows here — don't treat an empty Rates tab as proof the contract itself wasn't set up correctly.

Dates: what's on the tab

The Dates tab lists key milestone/obligation dates for the contract — Date, Type (e.g. "ETF Obligation Date"), Description, two Advance Notice columns, Certified, Completed, Closed, Responsible Party — with a row-level Delete button. Add Date adds a new row.

Contract Reopener: the signed report tied to renewal/trigger dates

Contract Reopener (FDD Reports Common 5.12, Reports > Employer) is a signed report listing contracts in their various trigger statuses along with reopener dates — the renewal-cycle counterpart to the milestone dates maintained on this Dates tab. It's selected by Contract Type, Advance Notice Month, and Advance Notice Year, and its output is sorted Business Agent (A-Z), then Contract Name, then Employer, then Jobsite, printing each employer/jobsite directly under the reopener date lines it belongs to — plus the contract's designated contact (name, title, address, phone) so an agent can confirm who to notify before filing the reopener. This has not been confirmed live in this project's UAT crawl — treat it as a signed requirement to validate, not a confirmed click-by-click path.

Things to watch out for

A future-dated wage rate doesn't apply to members until a daily batch job runs

Entering a wage rate with a future effective date does not update members' wage/dues rate immediately. A daily automated job checks jobsite wage rates for changes effective that day and updates the wage rate/dues rate for all associated members on the effective date itself. If "the new rate hasn't taken effect yet" and the effective date is still in the future (or was only today), that's expected — don't assume something is broken. (IUOE-2088)

An empty trade-code dropdown downstream is usually a Rates problem, not a UI bug

If a member's Add Work Record screen shows no trade codes for a jobsite tied to this contract, check two things here first: (1) does the jobsite have a contract attached at all, and (2) does that contract have an active, non-expired wage rate record for the trade code. A trade code only appears in that dropdown once a wage rate with a future (or current) end date exists for it — a contract with only expired/inactive rates shows no trade codes. (IUOE-2197, IUOE-2134)

The Dues Assessment report reads from work-record change history, not a dedicated history field

If a member's dues/wage rate looks wrong on the Dues Assessment report, the report is driven from the member's own work-record change history, not a separate assessment-history store. A rate fixed here on the contract doesn't retroactively correct a member's own stale change-history data — that's a per-member data correction, a distinct fix from a contract-rate correction. (IUOE-2131)

ETF Obligation Date does not follow the contract's rate-effective date

The ETF Obligation Date on this tab drives which month ETF invoices generate, and it is deliberately not kept in sync with the contract's rate-effective date — a jobsite's desired ETF billing month can legitimately differ from when a rate takes effect. On a contract renewal, explicitly check and (re)set the ETF Obligation Date yourself; don't assume it carried over with the new rate. (A one-time migration rule only auto-set this date where none existed yet — that rule doesn't apply going forward.) (IUOE-2683)

An error on Expiration Date entry may flash and disappear before you can read it

Entering a contract expiration date can occasionally show an error message that disappears before it's readable. This was not reproducible on followup and is not currently tracked as a confirmed defect — if you hit it, try the entry again before filing a new ticket. (IUOE-2233)

A long, hard-to-navigate contract dropdown has already been addressed

If you're hitting a long, unfiltered contract search dropdown or an oddly-labeled field (e.g. a "Sector" label), check the current release notes before assuming a fresh ticket is needed — contract search/labeling UX has had several targeted fixes already shipped (Contract Dropdown converted to typeahead; "Sector" renamed with Contract Type/Form fields introduced in its place).