Report a wrong figure or a rule that changed
Email info@bracketsight.com. It is a real address, read by the person who maintains the rule sets, and it is the only way to reach Bracketsight.
Every correction is checked against the primary source — the regulation, the IRS notice, the HHS guideline, the county assessor's own page — before anything changes. If the report holds, the rule file is updated, the pages that depend on it recompute, and the change is recorded in that tool's changelog with the date and the source. A correction is never taken on a secondary source, however confident it sounds.
What should you write about?
- A figure that looks wrong
- Send the inputs you used and the number you expected. Nothing you type into a tool is stored here, so the inputs are the only way to reproduce what you saw. A reproducible case is fixed faster than a description.
- A rule that has changed
- A new poverty guideline, a revised phase-out threshold, a county deadline that moved, a statute amended. A link to the primary source — the regulation, the notice, the county page — is the whole message.
- A rule that is missing
- A state clause, a county, an occupation code or an edge case the engine does not model yet. Say which one and what it should do.
- Anything else
- Press, licensing, a broken page, an accessibility problem. Accessibility reports go to the front of the queue.
What this address cannot do
No one here can look up your account, change your repayment plan, file your appeal, submit your return or speak to your servicer, employer, insurer or county on your behalf. There is no login to reset, because there are no accounts. Do not send account numbers, Social Security numbers, or loan or policy documents — they are not needed to fix a figure, and nothing sent by email can be processed under the no-storage promise the tools run on.
Who is on the other end?
Bracketsight is independent — not a lender, servicer, insurer, marketplace, payroll provider, county or contractor, and none of those pays for placement anywhere on it. How a rule gets from a regulation into a number here, how the site is funded, and which figures are still recorded as unverified are all set out on the about page, and the verification process itself — including the reviews that have not happened yet — on who writes and checks this.
What happens after you send it
A report about a figure is reproduced first: the inputs you sent are run through the same engine you used, and the result is compared with what you saw. If they differ, the bug is in the application; if they match, the question moves to the rule file behind the figure and the document that rule cites. Either way the answer names the document that was read and what it said, so a report that turns out to be wrong still tells you why.
A confirmed rule change is a smaller job than it sounds, and deliberately so. The value lives in one versioned file with its citation and its verification date; editing that file moves every page that depends on it at the next build, and the change is written into the relevant changelog with the date and the source. Nothing has to be hunted through prose, which is the reason corrections here are measured in hours rather than release cycles.
Bracketsight is an independent estimate engine. It is not financial, tax or legal advice, and it is not your servicer, your employer, your insurer or your county. Every figure is an estimate under current rules — confirm anything irreversible before you act on it.
Before you write: the register of unverified items may already list what you found, and each section keeps its own changelog of corrections — student loans, paycheck, health cover, property tax and trades. Terms the tools use are defined in the glossary.