Methodology – How We Build SASSA SRD R370 Guidance Pages

This page explains how HeAidsConference.co.za creates and updates SASSA SRD R370 guidance pages. We focus on user intent, exact portal wording, mobile-first readability, and clear next-step guidance.

Core Principles

  • User intent first: build pages around what the visitor is trying to solve now.
  • Exact wording matching: use the wording users actually see on SRD/appeals portals.
  • Status separation: keep processing statuses, decline reasons, and appeal outcomes separate.
  • Action-first structure: explain meaning, then show the correct next step.
  • Mobile-first format: cards, accordions, and stack-friendly lists instead of wide tables.

Page Types We Build

Status Hubs

Broad status pages that route users to the right next-step page quickly.

Decline Reason Pages

One decline reason per page with clear meaning + next action.

Appeal Pages

Appeal rules, timing, portal steps, and status checks without mixing decline wording.

Identity Verification Pages

Separate awaiting / failed / fixed guidance and link bridges.

Content Workflow

  1. Define the page intent and exact portal wording target.
  2. Map the user’s most likely next actions and confusion points.
  3. Build mobile-friendly sections (intro, quick bridge, meaning, next steps, FAQs).
  4. Add official links and internal links to the correct related pages.
  5. Review for wording collisions (decline vs appeal reasons, processing vs final outcomes).
  6. Publish and revise using feedback/corrections reports.

Quality Checks Before Publish / Update

  • Slug, heading, and page intent align
  • Internal links point to the correct page type
  • No page-specific CSS (uses global site stylesheet)
  • Mobile readability and button flow are clear
  • Scam warnings and non-affiliation language included where needed

Limitations

Our methodology improves clarity but does not replace official decisions or real-time access to your SASSA records. Always confirm on official portals.