Sources & Standards

Effective date: May 6, 2026

This page explains the kinds of sources, standards, and reference frameworks ExpertToolkit may rely on across calculators, converters, formulas, tables, and related structured pages. The exact source set for any one page may vary, but our goal is to anchor important logic in recognized and reviewable references rather than vague claims.

1. Why sources and standards matter here

A quantitative platform is only as trustworthy as the references behind its units, formulas, assumptions, datasets, and interpretations. That is why we treat provenance as part of product quality, not as a decorative footer note.

ExpertToolkit does not use the same source set for every page. A converter, finance calculator, health reference, and engineering formula may each require different authority checks. This page names the kinds of institutions and standards we look to when a topic calls for them.

2. Unit and measurement standards

For measurement-related logic, we aim to align with recognized unit definitions, conversion conventions, and physical measurement references. Depending on the topic, that may include standards bodies and measurement institutions such as:

• BIPM for SI-related unit definitions and measurement conventions;
• NIST for measurement standards, definitions, and technical references;
• ISO for internationally recognized technical, engineering, and measurement standards where applicable;
• other recognized metrology or standards bodies where a domain calls for them.

3. Scientific and engineering references

Formula pages, technical calculators, and engineering-style tools may rely on standard domain formulas, educational references, physical relationships, or commonly accepted technical conventions. Depending on the page, that may include academic references, textbooks, standards bodies, and industry norms.

• NIST, ISO, and similar standards bodies for measurement, engineering, and technical reference material;
• accepted scientific relationships, textbooks, and public technical references for formulas and derivations;
• domain-specific standards bodies where a calculator touches a regulated or safety-sensitive area.

4. Finance and economic references

Finance-oriented pages may depend on established calculation methods, public rates, official thresholds, tax conventions, inflation series, or other economic data sources. Where possible, we prefer references that are official, broadly accepted, or clearly documented.

• IRS materials for United States tax-related thresholds, concepts, and public guidance where relevant;
• FCA and other market regulators for jurisdiction-specific financial rules or consumer-finance context;
• CFA Institute conventions and other recognized finance education frameworks for broadly accepted finance formulas and terminology;
• official central-bank, government, or statistical sources for public rates, inflation, and economic datasets where a page depends on changing data.

5. Health and medical-adjacent references

Health-related tools may use public formulas, common screening frameworks, or widely known baseline references. These references can help explain how a result is computed, but they do not convert a page into medical advice. Users should still rely on qualified professionals for diagnosis and treatment decisions.

• WHO for global public-health definitions, screening context, and broad health benchmarks where relevant;
• CDC for United States public-health references and published health guidance where relevant;
• NHS and similar public health systems for widely-used explanatory references and patient-facing context where appropriate.

6. Government recall and safety records

Recall pages are different from the rest of the platform: they do not compute anything. Every fact on them is copied from a record published by a United States government agency, and every page links to that record so a reader can verify it directly. We do not scrape manufacturer sites, and we do not use non-official recall aggregators.

• NHTSA — vehicle safety recall campaigns, the official Do Not Drive and Park Outside advisories, the vPIC VIN decoder, owner complaints, and defect investigations.
• FDA — food, drug and medical device enforcement reports, including the agency's own Class I, II and III classification.
• USDA FSIS — meat, poultry and egg product recalls, which are published separately from the FDA and are attributed separately on our pages.
• CPSC — consumer product recalls published through SaferProducts.gov.

Agency wording is reproduced rather than rewritten. Where a recall page shows a hazard, a defect description or a remedy, those sentences are the agency's own and are attributed as such. Headings, layout and navigation are ours; the facts underneath them are not.

Recall severity is the one editorial judgement on those pages, because the four agencies do not classify the same way. The rule table is published in full, along with the signals it is allowed to use and the signals it is forbidden from inferring. Where an agency published no classification, our pages say “not classified by agency” rather than assigning a level.

Every recall page shows when its source was last synced successfully, in UTC. If a source has not synced successfully within 48 hours, the page carries a visible sync-delayed notice instead of presenting older data as current.

Recall information is provided for information only. It is not legal, medical or safety advice, and recall scope and remedies change. Confirm details with the manufacturer or the publishing agency before acting. For a specific vehicle, note that repair completion status is held by the manufacturer and is not published in any government feed.

7. Static references versus changing datasets

Some platform logic depends on relatively stable references, such as unit definitions or standard formulas. Other pages may depend on changing data, such as rates, thresholds, or public datasets that can be revised over time. We treat those two source types differently and expect freshness, versioning, and context to matter more for changeable data.

8. Page-level source specificity

This page describes the platform's general reference philosophy, not the complete citation list for every page. A strong page should still surface the standards or provenance relevant to that page's actual computation, dataset, or reference logic.

9. Limits and caution

Referencing a standards body or recognized source does not guarantee that every page is complete, current, or appropriate for every use case. Sources must still be interpreted, applied, and updated carefully. Where the platform has incomplete coverage or evolving logic, that should be treated honestly rather than implied away.

10. No endorsement or certification

Naming a standards body, regulator, institution, or public source does not mean that organization endorses ExpertToolkit, certifies our pages, or has reviewed our tools. These references describe the kinds of materials we use to guide computation, assumptions, and explanations where applicable.

11. Related trust pages

This page is part of the broader trust and transparency layer:

• About
• Methodology
• Editorial Policy
• Privacy Policy
• Terms of Service
• Disclaimer

12. Questions and corrections

If you believe a source description, standards reference, or provenance statement is unclear, missing, or wrong, please use the Contact page or email support@experttoolkit.net.