Editorial Methodology

ScoutMyTool publishes 1,576 free calculators, converters, and document templates. This page describes the editorial process behind them — how tools are researched, which authorities we cite, how formulas are verified, when tools are refreshed as regulations change, and what we do when we get something wrong. Understanding this process should let you decide how much to trust any specific result on our site. It should also make clear that a "free online calculator" is not necessarily a low-quality calculator when the process behind it is disciplined.

1. How a calculator is built

Every calculator starts from a primary authoritative source — not a blog post, not a Wikipedia article, not another calculator site. Concretely:

1. Research: identify the authoritative document (IRS Revenue Procedure for US tax; RBI notification or Ministry of Finance circular for India finance; ISO standard for math; WHO Technical Report for health; NIST SP 811 for units). Extract the exact formula + input ranges + edge-case rules.
2. Implementation: write the formula in TypeScript in the tool'scompute() function. Full source is committed to version control so any change can be traced.
3. Test against canonical examples: run the tool against worked examples from the authoritative source. For tax, we test against the IRS-published example cases in Publication 17. For medical, we test against clinical guideline examples. For unit conversion, we round-trip through NIST reference tables.
4. Cross-check against a reference implementation: verify the same input produces the same output on a widely-recognized site (bankrate.com, calculator.net, official government portals). Small rounding differences are acceptable; material differences trigger investigation.
5. Edge-case tests: zero inputs, extreme inputs (₹100 crore loan; 90-year-old age; 0% interest; leap-year Feb 29 birthdays; negative gains). If any edge case produces NaN, Infinity, or a nonsensical result, we clamp inputs or add a guard.
6. On-page prose: write the tool title, description, field hints, FAQ, and "How to use" steps — every piece is human-written, not AI-generated. Cite the authority in the About section.
7. Peer review: another editorial team member reviews the formula implementation + the on-page prose before shipping. Two-person review is default; tools with material tax or medical impact get a third-person review.
8. Ship: deploy via atomic-swap build with a healthcheck. Any deploy that fails the localhost healthcheck rolls back automatically.

2. What you see on every tool page

• Primary result — the headline number with the units and rounding that the source authority uses (not arbitrary precision).
• Breakdown — intermediate steps so the math is reproducible by hand.
• Field hints — small "?" tooltips explaining what each input means, its typical range, and where to find the value (e.g., "HRA component of your salary as shown on payslip").
• Amazon affiliate recommendations where topically relevant — clearly labeled with an AMAZON AFFILIATE badge and FTC disclosure. Recommendations are editorial (chosen for topical fit, not commission).
• Related tools — 4-8 hand-curated links to tools with the same audience/intent (not algorithmically generated).
• How to use — 3-5 step-by-step instructions.
• About this tool — 100-200 word explanation of what the tool does, the underlying formula, and the authority citation.
• Frequently asked questions — schema-marked (FAQPage JSON-LD) so search engines and AI assistants can quote them accurately.
• Reviewed by footer — links to /about page + "Last updated" date that reflects when the tool page (or its underlying data file) was last touched.

3. Authoritative sources by domain

The primary references we lean on, by tool cluster:

4. Review cadence

Every tool has a "Last reviewed" date in its footer. Review triggers:

• Regulatory change: RBI revises PPF rate, IRS releases new tax brackets, WHO updates BMI cutoffs — the affected tools are reviewed and updated within 14 days of official notification.
• Quarterly cycle: India small-savings rates (PPF, NSC, SCSS, SSY, POMIS, KVP) are officially revised every quarter. We check and update on the notification date.
• Annual cycle: India Union Budget (Feb) and US tax season (Jan) trigger comprehensive reviews of tax-related tools.
• User-reported error: within 7 days of a verified report (usually within 24 hours). See correction policy below.
• Year-stable tools: geometry, unit conversion, math — reviewed annually to check formula correctness and edge cases haven't regressed.

Automated nightly smoke testing runs against all 1,576 tools daily, verifying HTTP 200 response, presence of key HTML elements, and absence of error markers. Any regression is flagged the next morning and typically resolved within 24 hours.

5. Independent verification audits

Beyond the built-in review cycle, we periodically run formal cross-verification audits. Each audit takes the top N most-viewed tools, extracts the compute()function, independently re-implements it from the primary authoritative reference, and runs both implementations against a range of known-good test cases.

The most recent audit (2026-07-07, top 10 most-viewed calculators): all ten passed to the cent. Notably:

• Mortgage & Loan Calculators: verified against standard amortization formula and cross-checked with bankrate.com + CFPB Regulation Z spec on 6 test cases including zero-rate and extreme-rate edges.
• BMI Calculator: verified against WHO TRS 894 on 5 test cases (metric + imperial). Uses exact NIST conversion factors (0.45359237 kg/lb; 2.54 cm/inch).
• Age Calculator: verified across 7 tricky calendar cases including leap-year Feb 29 births, year-boundary transitions, and same-day cases. UTC-safe arithmetic with round-trip validation to prevent Feb 30 silent overflow.
• Compound Interest Calculator: verified against Excel FV() formula on 6 test cases across five compounding frequencies.
• Income Tax Calculator (US): 2026 brackets verified against IRS Rev. Proc. 2025-32 Section 4.01 Tables 1-4. Progressive bracket math verified via manual bracket-by-bracket calculation on 5 income scenarios.
• BMR / Calorie Calculator: all three formula options (Mifflin-St Jeor 1990, Harris-Benedict Roza-Shizgal 1984, Katch-McArdle) verified against original published equations.

Zero calculation bugs were found. Verification scripts are archived and can be re-run when underlying tool code changes. Test spec for any specific tool is available on request via contact@scoutmytool.com.

6. What we deliberately don't do

• No AI-authored calculators. Every formula, worked example, FAQ answer, and limitation note is written by a human. We use AI as spell-check and grammar assistant only, never as primary content author.
• No fabricated sources. Every citation links to a real document from a real authority. If we can't find an authoritative source for a calculation, we don't ship it.
• No professional advice. Our calculators are decision-support tools, not legal/medical/tax/financial advice. For consequential decisions, consult a licensed professional.
• No user data storage. Calculators run entirely in your browser. Nothing you type is sent to our servers. PDF and image tools that process files also run client-side; the small number of server-side exceptions (e.g. OCR on scanned PDFs) are clearly noted on the tool page.
• No affiliate links inside calculations. If we recommend a paid product (Amazon books, subscriptions), it's in a clearly-labeled Amazon Affiliate block AFTER the tool result, never woven into the computation itself.
• No dark-pattern ad placement. Ads are labeled, don't block the tool interface, and don't use fake-close-button or auto-scroll tactics. If we ever cross that line, tell us and we'll fix it.
• No SEO-driven tool proliferation. We publish a tool when it has a real editorial reason to exist, not when a keyword shows search volume. This is why we don't have 40 near-duplicate mortgage calculators like some competitors.
• No YouTube downloaders, DRM circumvention, or fake-document generators. Some categories draw traffic but carry legal/ethical concerns we don't want to normalize.

7. Editorial team & independence

ScoutMyTool is built by a small editorial team of software engineers and financial writers with backgrounds in enterprise fintech, tax consulting, and PDF/document technology. We work as a collective — no individual byline on tool pages — because tools are collaborative products: someone writes the formula, someone verifies against the source, someone reviews the prose, someone tests edge cases, someone maintains it as regulations change. The credit belongs to the process, not any single hand.

The site is self-funded through display advertising (Google AdSense — pending approval as of publication) and affiliate revenue (Amazon Associates via clearly-labeled product recommendations). We have taken no venture capital, no strategic investment from financial-services companies, no corporate sponsorships from banks or lenders. When our tools or articles recommend one approach over another (prepaying a home loan vs. investing; NPS vs. PPF; term insurance vs. endowment), the recommendation reflects editorial judgment based on math + regulatory reality — not a commercial relationship.

The corporate entity is Vertex Data Systems FZCO (Dubai). All revenue, taxes, and vendor relationships flow through this entity. There are no undisclosed affiliations, no shell structures, no hidden ownership.

8. Corrections & feedback

Our commitment when we get something wrong:

• All verified corrections are made within 7 days of the report; most within 24 hours.
• Every fixed tool page's "Last reviewed" date updates when substantive changes ship.
• Material corrections that affected prior computed results are called out in a short note at the top of the affected tool for at least 30 days.
• The fastest way to report an error is via the contact form or email contact@scoutmytool.com. Include: the URL, the input values you used, the incorrect output, and the reference you believe is correct.

9. Data handling

• Calculator inputs: computed locally in your browser. Never transmitted to our servers or third parties.
• PDF and image files: processed client-side in your browser using open-source libraries (pdf-lib, pdfjs). Files never leave your device. A small number of tools that require server-side processing (e.g. OCR on scanned PDFs) are clearly labeled — for those, files are processed and immediately deleted with no retention.
• Analytics: Google Analytics 4 captures page views, referrer, and country only. No form-content, no personal identifiers, no calculator input values.
• Advertising cookies: cookie consent banner offers explicit opt-out. Adherence to your consent choice is enforced through the entire ad stack.
• Full details in our Privacy Policy.

10. Legal disclaimer

Every calculator on ScoutMyTool is provided "as is" for informational purposes. While we take great care in sourcing, implementing, and verifying each tool, we make no warranty about the accuracy of results in any specific case. Users are responsible for checking outputs against their own circumstances and consulting qualified professionals before making consequential decisions (tax filing, medical treatment, investment allocation, legal contracts). ScoutMyTool disclaims liability for outcomes resulting from reliance on tool outputs. See our Terms of Service for the full legal position.

See also

• About ScoutMyTool — editorial mission and team
• Privacy Policy — what we collect and don't
• Terms of Service — the legal basis on which the site operates
• Contact — how to reach us and legal notice process
• Guides — long-form editorial content