Editorial Policy

Last updated: September 17, 2026

This page describes how IP1 Blog decides what to publish, how articles are checked, and what happens when we get something wrong. It is a commitment to readers, and we expect to be held to it.

What we publish

Explanatory guides to United States benefit programs: eligibility rules, application processes, appeal rights, and the practical decisions that sit around them. We choose subjects by one test — would knowing this change what a reader does next? An article that only restates what a program is called does not pass it.

How an article is built

• Research from primary sources. Regulation, agency manual or official program page. The hierarchy we use is set out in How we research.
• Separate the federal rule from the state rule. If a number varies by state, the article says so instead of presenting one state’s figure as national.
• Date every figure. Each dollar amount is tied to the period it applies to and linked to the official notice it comes from.
• Check the failure modes. What gets applications denied, what gets cases closed, what people routinely miss.
• Point to free expert help wherever a reader’s situation needs a person rather than a page.
• Review before publication, against the sources, by the editor.

Independence

Nobody pays for coverage on this site. We accept no payment, gift or consideration in exchange for writing about an organization, for a link, or for a favorable description. Advertising is sold programmatically by ad networks and is walled off from editorial decisions entirely — we do not know in advance which advertisers will appear on which article, and it would make no difference if we did.

We publish no sponsored posts, no guest posts, and no paid links. Unsolicited offers to buy any of these are declined without reply.

Use of AI

We use software tools, including AI assistants, for drafting support, editing and formatting. We do not publish machine-generated text that has not been checked line by line against primary sources by a person, and no figure reaches publication because a model produced it — every number is traced back to an official notice. Responsibility for everything published here rests with the editor named below, not with a tool.

Corrections

We will get things wrong. Rules change quietly, state practice diverges from federal text, and we make mistakes like anyone else. When that happens:

• Factual errors are fixed as soon as they are confirmed, not at the next convenient moment.
• Substantive corrections are disclosed on the article — what was wrong, what it now says, and the date. We do not silently rewrite a claim that readers may have acted on.
• Routine updates — a new year’s figures, a changed link — are reflected in the “last reviewed” date without a correction notice.
• If an article cannot be brought up to date, we unpublish it rather than leave stale benefits information online.

To report an error, use the contact form and choose “Correction or editorial feedback”, or write to contato@izzotodigital.com.br. Please include the article and, if you can, the official source that contradicts us — it is the fastest route to a fix.

Review schedule

Every article shows a “last reviewed” date. Articles are re-checked when the figures they rely on change — the SNAP adjustment each October, the poverty guidelines and Social Security amounts each January, Medicare amounts each January, tax figures each filing season — and at least once a year regardless.

Limits on what we do

We publish general information, not advice, and we cannot act on anyone’s case. The boundaries are set out in full in the Disclaimer, and they are not a formality — they are the difference between a guide that helps and a website pretending to be an agency.

Comments

Comments are closed across the site. On benefits articles, comment threads fill with Social Security numbers, case numbers, dates of birth and urgent requests for help that a comment box cannot answer. We would rather not have that information on our server, and we would rather not leave a request for help sitting unanswered in public. Write to us directly instead — every message is read.

Who is responsible