How OfferScope treats data
OfferScope is a planning tool, not a live payroll or housing database. The product should use public reference data for orientation, then encourage users to replace defaults with their real offer letter, lease quote, benefits deductions, commute cost, and savings target. This approach avoids fake precision. A city median can help a user start, but the apartment they actually sign decides the budget.
Salary references
For U.S. occupation and wage context, the most useful public source category is the Bureau of Labor Statistics Occupational Employment and Wage Statistics. BLS data can help frame typical pay by occupation and metro area. It should be supplemented with employer salary bands, job-board salary ranges, public compensation disclosures where available, credible salary surveys, and candidate-specific offer details.
OfferScope should not present salary presets as promises. A software engineer, product manager, or designer salary can vary by level, company stage, industry, bonus, equity, and location band. The salary field is user-editable because the offer letter is more important than any market average.
Housing and rent references
Rent should be verified with current market evidence before a decision. Useful source categories include Zillow-style rent indexes, Apartment List market reports, RentCafe market reports, live apartment listings, lease quotes, broker quotes, and neighborhood-specific searches. Citywide medians can hide the difference between a shared outer-neighborhood apartment and a premium central unit.
OfferScope city pages use rent ranges as planning bands. Users should replace them with the actual rent they would pay, plus utilities, parking, renter insurance, building fees, deposits, and move-in costs. This is especially important in New York, San Francisco, Los Angeles, Miami, Seattle, Austin, and Chicago, where neighborhood choice can change the result.
Population, commute, and cost context
Census and American Community Survey style datasets can help frame income, household structure, commuting patterns, and regional context. Cost-of-living references such as Numbeo-style indexes, local budget guides, and city economic reports can be useful, but they should not replace personal spending assumptions. A user with no car has a different cost profile than a user with parking, insurance, and a long commute.
Tax references
Tax assumptions should be checked against IRS guidance, state revenue departments, city tax resources where relevant, payroll calculators, and the employer's benefits materials. Federal tax, state tax, city tax, Social Security, Medicare, pre-tax retirement contributions, health premiums, and bonus withholding can all change take-home pay. That is why OfferScope exposes the tax-rate field instead of hiding it.
Data update policy
Salary markets, rent levels, and tax rules change. Source categories should be reviewed before launch and at least quarterly for major city pages. High-traffic city and career pages should be reviewed more often when housing markets or compensation bands move quickly. Last reviewed: May 25, 2026.
Limitations
Public datasets lag real-time market conditions. Apartment listings can change daily. Salary bands can vary by level and negotiation leverage. Tax assumptions can change by filing status and deductions. OfferScope therefore uses data to create a better first estimate, not a final answer. Users should verify numbers before accepting, relocating, signing a lease, or rejecting an offer.
Recommended verification workflow
Before accepting a real offer, users should verify five numbers. First, confirm base salary and whether bonus is guaranteed or target-based. Second, estimate take-home pay with federal, state, city, payroll, and benefit deductions. Third, collect actual rent options from live listings or lease quotes rather than relying only on city averages. Fourth, add transportation, insurance, utilities, debt, and savings. Fifth, test a conservative version where rent or first-year costs are higher than expected.
Source categories by decision type
| Decision | Useful source category | How to use it |
|---|---|---|
| Salary market | BLS, employer bands, salary surveys, job postings | Check whether the offer is broadly competitive. |
| Rent | Zillow-style indexes, Apartment List, RentCafe, live listings | Replace presets with realistic lease options. |
| Tax | IRS, state revenue departments, payroll calculators | Estimate take-home pay before spending decisions. |
| Living cost | Census/ACS, local guides, Numbeo-style indexes | Frame commute, household, and regional cost assumptions. |
Editorial standard
OfferScope pages should name source categories clearly and avoid pretending that a preset is a verified live quote. When a city page says a rent range is typical, it should be understood as a planning band. When a career page discusses salary, it should be treated as an evaluation framework rather than a compensation promise. The product earns trust by making assumptions visible and easy to replace.
Pages should also include a review date so users and search engines can see whether assumptions are maintained. If a source category becomes outdated or unavailable, the page should be revised rather than leaving stale guidance in place. This is especially important for rent, tax, and salary topics because they can change quickly by city and year.