Methodology
How make100k turns disclosure rows into salary intelligence
The province publishes annual salary disclosure files. make100k preserves those source facts, resolves them into persistent people and employers, then adds comparable metrics: salary history, raises, ranks, percentiles, municipal summaries, job-title distributions, and inflation-adjusted thresholds.
Row-count parity
Annual source files are counted before enrichment. A build cannot ship when a source year loses or gains rows unexpectedly.
Conservative merges
A false person merge is treated as worse than a false split. Same-name collisions are separated and flagged instead of silently combined.
Source provenance
Every public money page states the source, latest year, resolution type, and whether the entity is reviewable.
Thin-page controls
Single-year or low-support entities can render for users while staying out of the index until they have enough substance.
Source data
make100k uses Ontario Public Sector Salary Disclosure data published under the Open Government Licence - Ontario. Source columns include name, employer, position, salary, taxable benefits, and disclosure year. The site does not estimate undisclosed income, infer private compensation, or add data from unofficial lists.
Entity resolution
Raw employer strings are normalized into canonical employers while preserving aliases. Person records are clustered conservatively within employer and year context, with same-name collisions flagged for review. The result is a navigable graph: one person page can show a career path across years, while one employer page can survive naming variants and reorganizations.
Metrics
Person pages calculate year-over-year salary deltas, employer percentiles, title ranks, career ranges, and total disclosed earnings. Employer, title, city, sector, and year pages calculate headcount, medians, percentiles, distributions, and peer lists from the same resolved records. Inflation context uses annual CPI-style threshold enrichment so the unchanged $100,000 line can be compared across time.
Indexing rules
The site is intentionally selective about pages sent to search engines. Sitemaps prioritize multi-year people, employer profiles, meaningful title clusters, municipalities, years, and durable utility pages. Thin entities can still resolve for users, but low-support pages receive noindex or stay out of sitemap generation until there is enough evidence to make them useful.
Corrections
Every person page includes a correction path. Corrections are handled by fixing the underlying resolution or source mapping, then regenerating affected public pages, source notes, and crawler-visible pages so the site stays aligned.
Contains information licensed under the Open Government Licence - Ontario. make100k adds entity resolution, quality checks, and derived salary intelligence.