Ipsoot.Data

What We’ve Built / Contracts

Comparing wages and terms across contracts

Wage scales locked inside scanned documents might as well not exist.

Any PDFtyped, scanned or faxed decades ago
Wageswage tables pulled out as data
Compareemployers and locals, side by side

The problem

Collective bargaining agreements come as PDFs: some typed, some scanned, some faxed decades ago. The expiration dates, wage tables and contract language inside them can’t be searched, compared or counted.

What we built

A system that reads each contract, however it was made, and turns it into data: who the parties are, when it starts and expires, its wage tables, and every article.

What it means at the table

Bargaining arguments are built on comparisons, and a comparison is only as good as the contracts behind it. Once wage tables and terms come out as data, they can be lined up side by side across employers and locals instead of read one PDF at a time:

  • Area comparables. What other employers in the same city, county or region pay for the same work, so the team can show where its members stand in the local labor market.
  • Similar employers. Employers of the same kind and size, wherever they are: counties of similar population, other school districts, hospitals or carriers. These are often the comparisons fact-finders and interest arbitrators look to.
  • The same employer’s other contracts. What the employer has already agreed to with its other bargaining units or at its other locations.
  • Over time. How wages and terms at comparable employers have moved from one contract to the next, so a settlement can be measured against the pattern, not a single year.
  • More than wages. Step structures, shift differentials, health and retirement contributions, leave, and the contract language each employer uses on the same issue.

Our comparables tool puts this to work: it suggests comparable employers, ranks your unit against them and costs the catch-up.