Editorial Policy

How we write

Every guide on this website is written to answer a real question that South Africans ask about SASSA — in plain language, with the direct answer first, followed by the steps, the requirements, and the common problems. We write for ordinary readers, including people who are not familiar with government terminology, and we explain difficult terms when we use them.

A guide starts with the question, not with the topic. Before writing, the writer asks: what is the person reading this actually trying to do? Are they checking a status for the first time? Have they been declined and want to know why? Has their payment not arrived and do they need to know what to do next? The guide is then built around that situation, in the order a real person would follow it. The direct answer comes first, so that a reader in a hurry — or a reader on a phone with limited data — can get the answer without scrolling through pages of background. The detail follows for readers who want the full picture: the steps, the requirements, what can go wrong, and what to do about it.

We write in plain South African English. Sentences are kept short. Jargon is avoided wherever a plain word will do, and when a government term has to be used — a means test, a reconsideration, a status message — it is explained the first time it appears. We do not write to impress, and we do not write to fill space. Every paragraph should earn its place by answering something the reader needs to know. If a sentence does not help the reader, it does not belong in the guide.

Who we write for

We write for the people who actually deal with SASSA: applicants, grant recipients, parents and caregivers, older persons, people with disabilities, and the family members and community helpers who assist them. Many of our readers are applying for a grant for the first time. Many are reading on a phone, often on a slow or expensive connection. Some are reading in a second or third language. Our writing has to work for all of them.

That shapes everything about how a guide is written. Steps are numbered so they are easy to follow on a small screen. The most important facts — the official website addresses, the toll-free number, the key requirements — are placed where they are easy to find, not buried in a long paragraph. Warnings about scams are repeated where they matter, because a reader who only reads one section should still see them. And the tone is respectful: applying for a grant is not easy, and the people who do it deserve clear information, not condescension.

We do not write for SASSA, for the government, or for other websites. We write for the reader in front of us. If a guide is clear to a first-time applicant reading on a phone, it has done its job. If it is only clear to someone who already understands the system, it has not — and it needs to be rewritten.

How we research

We research official sources first: sassa.gov.za, srd.sassa.gov.za, services.sassa.gov.za, gov.za and dsd.gov.za. Grant amounts, payment dates, eligibility rules, deadlines and contact details are taken from those sources or from official government statements. We do not copy competitor articles, and we do not invent facts, figures, dates, requirements or links.

Research for a guide begins with the official source. The writer reads the relevant official SASSA page or government notice first, then checks whether the same information appears consistently across the official portals. Only after that does the writer consider how the question is usually asked — because the official page does not always use the same words as the person asking. Our job is to connect the two: the official meaning, expressed in the words people actually use.

We do not copy other websites, and we do not present another website’s claim as our own. Where a fact matters — a grant amount, a payment date, a deadline, a contact number — it must come from an official source, or it must be clearly marked as unverified. We check the official source ourselves rather than trusting a summary of it, because summaries can be wrong, out of date, or written about a different grant. If the official source is unclear, the guide says so, rather than filling the gap with a guess.

Fact-checking before publication

No guide is published without being checked. Before a guide goes live, the writer checks the important facts in it against the official source: the amounts, the dates, the deadlines, the requirements, the contact details, and the links. The links in a guide are checked to make sure they lead to the official pages they claim to lead to, and that the anchor text describes the destination honestly. The tool that sits with a guide, where one exists, is checked against the same verified facts.

Checking is not a single step at the end — it happens throughout the writing. When a writer finds two official sources that disagree, the disagreement is not hidden: the guide flags it, and the writer looks for the more recent or more specific official source. When a figure has changed recently, the writer checks whether the guide reflects the change. When a reader reports an error after publication, the same checking process starts again: the official source is consulted, the fact is verified, and the guide is corrected if the report is confirmed.

We do not invent the things we cannot verify. We do not state processing times, office hours, hotline numbers, or USSD codes that we could not confirm from an official source. We do not invent grant amounts, payment dates, eligibility rules, or deadlines. We do not invent links, and we do not invent quotes or statements from SASSA. A guide that says “we could not verify this” is more honest — and more useful — than a guide that gives a confident answer built on a guess.

When we are not sure

SASSA information changes, and official sources sometimes conflict. When we cannot verify a claim from an official source, we say so plainly in the guide — marked [VERIFY] — instead of presenting it as fact. We do not state processing times, USSD codes, office hours or hotline numbers that we could not confirm officially.

Uncertainty is not a failure of research; it is a fact about the subject. SASSA updates its rules and procedures, official pages are revised, and some details — such as how long a particular step takes — are simply not published by SASSA at all. When we meet that kind of gap, we have two choices: guess, or say we do not know. We always choose the second. A guide that tells you plainly that a processing time is not published is protecting you from acting on a made-up number.

The [VERIFY] mark is our way of being honest about those gaps. Where you see it in a guide, it means the information next to it could not be confirmed from an official source at the time of writing, and you should check it with SASSA before relying on it. We would rather you see the mark and check, than read a smooth, confident sentence and never realise it was uncertain. If you can point us to an official source that resolves a [VERIFY] item, please tell us through the Contact Us page — that is exactly the kind of message that makes the guides better.

Updates and corrections

Guides are not written once and forgotten. SASSA rules change, amounts are revised, payment schedules are updated, and official portals change their steps. We review our guides on an ongoing basis, and we update them when the official source changes or when a reader tells us that a step no longer matches what the official portal shows.

Corrections follow a simple process. First, the report is read and the official source is checked — we do not change a guide on the basis of an unverified claim, even a well-meaning one. Second, if the error is confirmed, the guide is corrected, and the correction is checked again before the guide is republished. Third, where a change is significant — for example, a changed deadline or a changed requirement — the guide is updated to reflect the new official position, not patched with a note that contradicts the rest of the text. Where official sources themselves disagree, or where a fact cannot be confirmed, the guide will say so rather than quietly choosing one version.

Readers are an essential part of this process. You use the official portals every day, and you often notice a change before we do. If a guide is wrong, if a step has changed, or if an official rule has been updated and our guide has not caught up, please tell us through the Contact Us page. Tell us which guide you were reading, what you found, and — if you can — where on the official SASSA website the correct information appears. We read every message, and we correct confirmed errors.

Independence

This website is independent. It is not written, reviewed or approved by SASSA or by any government department, and no government body endorses it. Our guides link to official SASSA websites so readers can confirm information at the source.

Independence is what allows us to write honestly. Because no government body reviews our guides, we can say when a process is confusing, when a status message is unclear, or when an official page does not answer the question people are asking. We can also choose which questions to answer, based on what readers actually ask, rather than on what an official body would prefer to highlight. That freedom comes with a responsibility: we must be careful, check our facts, and correct our mistakes — because there is no official body standing behind our words.

Independence also means our guides are not official statements. They should never be quoted as if SASSA said them, and they should never be treated as a substitute for the official answer. When a guide and an official SASSA page disagree, the official page is the one to follow. Our guides exist to help you understand the official process and to point you to the official source — not to replace it.

No paid placement

No guide, tool or link on this website is paid placement. We do not accept payment to recommend a service, and we do not publish sponsored content as editorial content.

This rule is absolute. Nobody can pay to have a guide written about their service, to have a link placed in a guide, to have a tool recommend them, or to have a product or service presented as if it were our own editorial judgement. If a guide recommends an official channel — for example, the SASSA toll-free line or the official SRD portal — it does so because that channel is the official one, not because anyone paid for the recommendation.

The same applies to the links in our guides. We link to official SASSA and South African Government websites because those are the sources readers need to confirm information. We do not sell links, we do not exchange links for payment, and we do not publish links to commercial services in return for money. If you ever see a link on this website that looks like an advertisement or a paid recommendation, please tell us through the Contact Us page — it does not belong here, and we will remove it.

Reader feedback

Our readers are our best editors. You read the guides in real situations, with real applications and real payments at stake, and you notice things we cannot see from behind a desk: a step that has changed on the official portal, a status message we have not explained, a warning that needs to be clearer, or a question that none of our guides answers yet.

We welcome all of it — corrections, questions, suggestions for new guides, and criticism of guides that are unclear. The best way to send feedback is through the Contact Us page. Tell us which guide you were reading and what you found, in your own words; you do not need to write formally. If you are reporting an error, it helps to tell us where the correct information appears on the official SASSA website, but it is not required — we will check the official source ourselves.

We read every message, and we act on the ones that point to a genuine error or a genuine gap. We cannot reply to every message in detail, and we cannot help with personal SASSA matters — we cannot check your status or act on your application — but every message is read, and the ones about our own guides shape what we write and fix next. Thank you for helping us make SASSA information clearer for everyone who reads it.

How guide topics are chosen

We choose guide topics from the questions people actually ask. When readers write to us, when a status message confuses many people at once, when a SASSA rule changes, or when a common problem appears again and again, that is a signal that a guide is needed — or that an existing guide needs to be rewritten. We do not choose topics because they are popular with advertisers or because another website has covered them; we choose them because a real person needs the answer.

Each guide covers one question, not a whole subject. A guide about payment dates answers when payments are expected and what to do if a payment has not arrived; it does not try to explain every grant at the same time. A guide about changing banking details covers that one process, step by step, including what can go wrong. Keeping guides focused is what makes them useful: a reader can find the answer to their question without reading through information about ten other things first.

We also choose what not to write. We do not write guides that repeat rumours about grants, and we do not write guides based on claims we cannot verify from an official source. If a question is being asked widely but the official answer is not available, we would rather wait — or write a guide that says plainly what is not yet known — than publish a confident answer built on guesswork. If there is a question you think we should cover, tell us through the Contact Us page: reader suggestions are one of the main ways new guides are chosen.