JobFrame · Schema Map
Bring your roster and any documented job schema.
We map every job between them through the JobFrame canonical reference: the full crosswalk, a confidence band and evidence on every match, a review queue for the borderline ones, and an honest no-match list — never a forced match.
What we keep, and what we never keep
What we keep, and what we never keep: the mapping we build between your data and the JobFrame reference is yours — it stays private to your account, and you keep read access to it even if you leave. If the schema you upload belongs to a survey vendor (Radford, Mercer, WTW, CompAnalyst, or similar), we map against it only for you, under your license: vendor structures are never added to our public reference, our title dictionary, or anything another customer can see. Aggregated pay observations contribute to our cross-client benchmarks only after job labels are converted to our own canonical codes and small groups are suppressed (minimum-count gating) — never as your raw rows, and never carrying a vendor's codes or titles.