Policy
Corrections Policy
India Toolbox aims to keep calculations, guide framing, and generator workflows accurate and clearly limited. When a page is wrong, misleading, outdated, or unclear in a material way, it should be corrected.
Correction requests can be sent to [email protected].
What counts as a correction
- A factual error in a guide or policy page
- A misleading or outdated slab, rate, threshold, or calculation assumption
- A document workflow explanation that misstates what the output is for
- A broken or incomplete generator behavior that changes the meaning of the result
What counts as an update instead
Some changes are not corrections in the narrow sense. For example, a new financial year, a changed marketplace assumption, or a broader content rewrite may be handled as an update rather than as a correction.
The difference is practical: a correction fixes a wrong or misleading statement, while an update reflects new rules, new structure, or improved explanation.
How correction requests are reviewed
Requests are checked against the live page, the visible assumptions on that page, and the most relevant source or workflow context. If the issue is real, the page may be corrected directly, clarified with narrower wording, or paired with a stronger limitation note.
If the issue depends on a scenario that falls outside the page scope, the fix may be to make the page boundary clearer rather than to claim support for a broader case it does not truly handle.
How substantive changes are handled
When a correction changes the meaning of a result materially, the page should be updated with clearer review text, stronger explanation, or both. Sensitive pages may also have their review date refreshed when the correction is published.
The goal is not silent cosmetic cleanup. It is to keep the page trustworthy for the next user who lands on it.
Useful links
Keep key pages easy to find.