Supported Agreements

Built around the agreements
power workers actually work under.

GridPay does not treat an enterprise agreement as a list of hourly rates. Supported agreements are implemented within defined worker and scenario boundaries so supported overtime, callbacks, allowances and other agreement-specific entitlements can be calculated consistently.

GridPay approach

Deep agreement implementation over broad, shallow coverage.

Every public agreement page explains what GridPay supports, who is currently within scope, and where the boundary stops.

Launch agreement coverage

Know exactly what supported means.

Launch agreementSouth Australia

Utilities Management Pty Ltd Enterprise Agreement 2025

Bounded support for defined Utilities Management worker classifications and scenarios.

Ordinary earningsOvertimeCallbacksAvailabilityPublic holidaysMealsTravel / LAFHAAllowances

Defined supported worker and scenario boundaries apply.

View agreement support
Launch agreementQueensland

Energy Queensland Union Collective Agreement 2024

Bounded support for defined Energy Queensland worker profiles and validated work arrangements.

Ordinary earningsOvertime / recallEmergency workMealsPublic holidaysWorking away

Defined supported worker and scenario boundaries apply.

Detailed public coverage will be published when the launch information for this agreement is ready.

What support means

More than storing a rate.

01

Agreement rules

Defined calculation rules, not generic wage multipliers.

02

Explicit boundaries

Unsupported combinations are surfaced rather than silently calculated.

03

Independent implementation

Source instruments are identified without implying employer, union or Fair Work endorsement.

Expanding agreement coverage

Deep implementation first. Deliberate expansion next.

GridPay is starting with a focused set of Australian power-industry enterprise agreements and will expand coverage over time.

New agreements will only be listed as supported after their calculation rules, rates and supported boundaries have been implemented and validated.