Editorial Policy

Source-first publishing

Occupation descriptions, skills, job titles, education data, and experience data are based on identified occupational datasets or other clearly named sources. Source fields are normalized for presentation, but unsupported salary, growth, licensing, workplace, or outcome claims are not added to fill gaps.

When standardized education or experience data is unavailable, the page says so and may offer deterministic links to other profiles. “Not reported” communicates missing comparison data; it is not replaced with a guess.

Explanatory writing

Explanatory modules may reorganize source descriptions and skill information into plain-language context. They must distinguish broad patterns from requirements, avoid duplicating the source description, and state that responsibilities can vary by industry, employer, and seniority. They must not imply first-hand testing, interviews, or personal experience that did not occur.

Automated tools may assist with drafting, formatting, consistency checks, or large-scale validation. Their output remains subject to source constraints, deterministic checks, and editorial review. Tool use is never a source of occupational facts by itself.

Comparisons and related careers

Related-career and comparison modules use the same stable set for a given occupation. Matching can consider field, source description, skill overlap, and available preparation data. It is an information-retrieval aid, not a ranking, compatibility score, labor-market forecast, or recommendation.

Attribution and independence

Sources, official graphics, and third-party marks are attributed where required. Source identification does not imply that a government agency, dataset provider, employer, school, advertiser, or linked organization sponsors or endorses the site. Advertising, when present, is separated from editorial decisions and labeled as advertising.

Review, updates, and corrections

Content is reviewed for source fidelity, required phrases, word ranges, missing-data handling, internal-link integrity, responsive presentation, and unsupported claims. Updates may follow a source refresh, a verified correction, a product requirement, or a technical change. Not every page is updated on a fixed schedule.

Correction requests can be sent to [email protected]. Include the page URL, the disputed material, and a reliable supporting source. We review substantive reports and may correct, clarify, add attribution, or retain the existing text when the evidence does not support a change.