Policy
Review and Methodology Policy
India Toolbox is designed to keep calculation logic and workflow boundaries visible. This policy explains how pages are scoped, how assumptions are chosen, and how estimate-first pages differ from official systems.
The aim is practical clarity, not fake universality.
How calculators are scoped
A calculator is scoped around a clear planning job. Salary pages are meant for take-home estimation and regime comparison. Loan pages are meant for affordability and interest planning. Seller-fee pages are meant for margin estimation before listing. A page should not imply support for scenarios it does not truly model.
If the right answer depends heavily on employer policy, marketplace behavior, state rules, or live tariffs, the page should expose that limitation rather than hide it behind a generic result.
How assumptions are chosen
Assumptions are chosen from the most relevant public or workflow-specific source available for the page type. For some pages that means official policy framing or public slab logic. For others it means a clearly labelled static assumption used for planning rather than for official reconciliation.
An assumption is only acceptable if it is understandable, explainable, and useful to a real user. If a page needs live data or scenario-specific interpretation to be reliable, it should say so explicitly.
Estimate-only pages
Some pages are intentionally estimate-first. Seller fees, stamp duty, construction cost, tariff-driven household pages, and similar tools may be valuable for budgeting even when they cannot offer complete official precision from one static form.
Those pages are reviewed on a different standard from a pure math calculator. The test is whether the limitation is honest, the workflow is still useful, and the page avoids fake precision.
Document generators
A generator is reviewed both for output structure and for workflow honesty. A rent receipt generator should explain that it creates a receipt and not proof of payment. An invoice generator should explain that it creates a draft and does not replace filing or ERP workflows.
The generated output should be useful, but the page should not overstate what that usefulness means.
Change-sensitive maintenance
Pages tied to tax rules, GST framing, or marketplace fee assumptions are reviewed more aggressively than stable arithmetic pages. They are more likely to need refreshed dates, narrower wording, or stronger source framing after changes in policy or platform behavior.
If a page cannot be kept honest under changing conditions, it should be narrowed or de-emphasized instead of being left with stale implied certainty.
Useful links
Keep key pages easy to find.